System and method for providing AC jumper management and identifying AC jumper topology

ABSTRACT

A server rack includes a power mapping module, a power receptacle that includes a power tine communication module wherein the power receptacle is uniquely associated with a rack unit of the server rack and is collocated with the associated rack unit, and a server coupled to the power mapping module via a management network, wherein the server asserts an interrupt request to the power mapping module via the management network. The power mapping module sends a unique identifier via the first power tine communication module in response to receiving the interrupt request. The server receives the unique identifier via the second power line communication module and sends the unique identifier to the power mapping module via the management network. The power mapping module determines that the server is installed into the rack based upon the receipt of the unique identifier.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.14/199,660, filed Mar. 6, 2014, entitled “System and Method forProviding a Server Rack Management Controller,” invented by John R.Palmer et al., and assigned to the assignee hereof.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, andmore particularly relates to a system and method for providing AC jumpermanagement and identifying ac juniper topology in a server rack.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements may varybetween different applications, information handling systems may alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information may be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing,reservations, enterprise data storage, or global communications. Inaddition, information handling systems may include a variety of hardwareand software resources that may be configured to process, store, andcommunicate information and may include one or more computer systems,data storage systems, and networking systems.

A data center is a facility to house a group of networked informationhandling systems typically used by organizations for the remote storage,processing, or distribution of large amounts of data, and includesassociated components, such as telecommunication systems, storagesystems, power supplies, environmental controls, and securityinfrastructure. A data center includes a group of server racks thathouse the information handling systems, and that are located on floortiles of a raised floor. A space below the raised floor can be utilizedto provide an air flow from an AC system to the server racks.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are shown and described with respectto the drawings presented herein, in which:

FIG. 1 is an illustration of a data center according to an embodiment ofthe present disclosure;

FIG. 2 is a block diagram of a data center floor including passive floortiles according to an embodiment of the present disclosure;

FIG. 3 is a block diagram of a portion of the data center floor of FIG.2;

FIG. 4 is a block diagram of an active floor tile including a tilemanagement controller according to an embodiment of the presentdisclosure;

FIGS. 5-8 are block diagrams of data center floors according to variousembodiments of the present disclosure;

FIG. 9 is a block diagram of a server rack including a rack managementcontroller according to an embodiment of the present disclosure;

FIG. 10 is a block diagram of a data center including an active floortile and a server rack according to an embodiment of the presentdisclosure;

FIGS. 11-15 are illustrations of server racks according to variousembodiments of the present disclosure;

FIG. 16 is an illustration of the data center of FIG. 1 including an airflow from a data center AC system;

FIG. 17 is a block diagram of an active floor tile including a tilemanagement controller and a vent according to an embodiment of thepresent disclosure;

FIG. 18 is a block diagram of a server rack including a rack managementcontroller according to an embodiment of the present disclosure;

FIG. 19 is a block diagram of an active floor tile including a powergenerator according to an embodiment of the present disclosure;

FIG. 20 is a block diagram of an active floor tile including a weightsensor according to an embodiment of the present disclosure;

FIG. 21 is a block diagram of a server rack including a weight sensoraccording to an embodiment of the present disclosure;

FIG. 22 is an illustration of a server rack foot assembly including aweight sensor according to an embodiment of the present disclosure;

FIG. 23 is an illustration of a server rack foot assembly including alevel sensor according to an embodiment of the present disclosure;

FIGS. 24 and 25 are illustrations of a server rack including a rackmanagement controller and a balance interlock module according to anembodiment of the present disclosure;

FIG. 26 is an illustration of a server rack including a rack managementcontroller, a panel detection module, and a panel ground detectionmodule according to an embodiment of the present disclosure;

FIG. 27 illustrates data center 100 of FIG. 1 including a data centermanagement appliance;

FIG. 28 is a flowchart illustrating a method for programming a passivefloor tile according to an embodiment of the present disclosure;

FIG. 29 is a flowchart illustrating a method for communicatinginformation from a passive floor tile to a server rack according to anembodiment of the present disclosure;

FIG. 30 is a flowchart illustrating a method for pre-programming anactive floor tile according to an embodiment of the present disclosure;

FIG. 31 is a flowchart illustrating a method for networking active floortiles according to an embodiment of the present disclosure;

FIG. 32 is a flowchart illustrating a method for communicatinginformation between an active floor tile and a server rack according toan embodiment of the present disclosure;

FIG. 33 is a flowchart illustrating a method for finding a physicallocation of equipment in a server rack according to an embodiment of thepresent disclosure;

FIG. 34 is a flowchart illustrating a method for providing a real timeclock to equipment in a server according to an embodiment of the presentdisclosure;

FIG. 35 is a flowchart illustrating a method for mapping network portsand vLANs in a server rack according to an embodiment of the presentdisclosure;

FIG. 36 is a flowchart illustrating a method for mapping powerconnections in a server rack according to an embodiment of the presentdisclosure;

FIG. 37 is a flowchart illustrating a method for managing the runningaverage power in a server rack and a data center according to anembodiment of the present disclosure;

FIG. 38 is a flowchart illustrating a method for operating servers invarious standby modes according to an embodiment of the presentdisclosure;

FIG. 39 is a flowchart illustrating a method for operating a floor tilewith an active vent according to an embodiment of the presentdisclosure;

FIG. 40 is a flowchart illustrating a method for closed loop thermalcontrol of a server rack and a data center according to an embodiment ofthe present disclosure;

FIG. 41 is a flowchart illustrating a method for preemptive/proactivecooling of a server rack and a data center according to an embodiment ofthe present disclosure;

FIG. 42 is a flowchart illustrating a method for active power generationfor an active floor tile according to an embodiment of the presentdisclosure;

FIG. 43 is a flowchart illustrating a method for reporting the weight ofa server rack according to an embodiment of the present disclosure;

FIG. 44 is a flowchart illustrating a method for providing a positionindication for leveling feet of a server rack according to an embodimentof the present disclosure;

FIG. 45 is a flowchart illustrating a method for leveling a server rackaccording to an embodiment of the present disclosure;

FIG. 46 is a flowchart illustrating a method for locking equipment intoan unbalanced server rack according to an embodiment of the presentdisclosure;

FIG. 47 is a flowchart illustrating a method for detecting a panel in aserver rack according to an embodiment of the present disclosure;

FIG. 48 is a flowchart illustrating a method for managing a data centeraccording to an embodiment of the present disclosure;

FIG. 49 is a flowchart illustrating a method for setting up a datacenter according to an embodiment of the present disclosure;

FIG. 50 is a block diagram illustrating a method for repairing a datacenter according to an embodiment of the present disclosure;

FIG. 51 is a block diagram illustrating a generalized informationhandling system according to an embodiment of the present disclosure;and

FIG. 52 is a flowchart illustrating a method of determining the physicallocation of a server in a server rack according to an embodiment of thepresent disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachings,and should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe used in this application. The teachings can also be used in otherapplications, and with several different types of architectures, such asdistributed computing architectures, client/server architectures, ormiddleware server architectures and associated resources.

FIG. 1 illustrates an embodiment of a data center 100 including serveraisle 110, a floor 130, a data center management controller (DCMC) 150,a sub-floor 160, a cold aisle 170, and a hot aisle 180. One or more ofthe elements of data center 100 can be realized as an informationhandling system. For purpose of this disclosure an information handlingsystem can include any instrumentality or aggregate of instrumentalitiesoperable to compute, classify, process, transmit, receive, retrieve,originate, switch, store, display, manifest, detect, record, reproduce,handle, or utilize any form of information, intelligence, or data forbusiness, scientific, control, entertainment, or other purposes. Forexample, information handling system 100 can be a personal computer, alaptop computer, a smart phone, a tablet device or other consumerelectronic device, a network server, a network storage device, a switch,a router, or another network communication device, or any other suitabledevice and may vary in size, shape, performance, functionality, andprice. Further, an information handling system can include processingresources for executing machine-executable code, such as a centralprocessing unit (CPU), a programmable logic array (PLA), un embeddeddevice such as a System-on-a-Chip (SoC), or other control logichardware. An information handling system can also include one or morecomputer-readable medium for storing machine-executable code, such assoftware or data. Additional components of information handling system100 can include one or more storage devices that can storemachine-executable code, one or more communications ports forcommunicating with external devices, and various input and output (I/O)devices, such as a keyboard, a mouse, and a video display.

Server aisle 110 includes server racks 112, 114, 116, 118, and 120 thatoperate to perform the data storage and processing functions of datacenter 100. Floor 130 is a false-floor that forms a platform above aground level floor, crating sub-floor 160, an area between floor 130 andthe ground level floor. Sub-floor 160 provides for power routing andcabling for servers 112, 114, 116, 118, and 120, and acts as a conduitfor air conditioning (AC) to provide temperature controlled air flow tothe servers. As such, floor 130 includes floor tiles 132, 134, 136, 138,and 140 that each include vents that permit the temperature controlledair to pass from sub-floor 160 to cold aisle 170. There, the temperaturecontrolled air is drawn through the equipment in server racks 112., 114,116, 118, and 120 to cool the equipment, and the air flows out the backof the server racks, removing the heat from the equipment, and passingto hot aisle 180, where the hot air is recirculated through an ACsystem. The skilled artisan will recognize that other floorconfigurations than the illustrated raised floor configuration shownherein can be utilized in combination with the teachings of the presentdisclosure, as needed or desired. Further, the skilled artisan willrecognize that other air flows than the air flows from the floor to thecold aisle to the hot isle as illustrated herein can be utilized incombination with the teachings of the present disclosure, as needed ordesired.

In an embodiment, DCMC 1150 operates to provide a management network forthe equipment in server racks 112, 114, 116, 118, and 120. For example,one or more of the elements of server racks 112, 114, 116, 118, and 120can include a service processor such as a baseboard managementcontroller, an Integrated Dell Remote Access Controller (iDRAC), anotherservice processor, or a combination thereof, such that DCMC 150 canremotely manage the equipment in the server racks. An example of a DCMCincludes a dedicated hardware device, a software stack on a dedicatedserver, a software stack on a server of data center 100, or otherhardware, software, or firmware located in the data center or remotefrom the data center, as needed or desired.

In a particular embodiment, the floor tiles operate to provideinformation to respective server racks. In a first case, the informationis communicated via a passive communication channel. In another case,the information is communicated via an active communication channel, andthe floor tiles include a tile management controller (TMC). In anotherembodiment, the information is provided to a rack management controller(RMC). In either of the above embodiments, each TMC can be incommunication with DCMC 150, each RMC can be in communication with theDCMC, or both the TMCs and the RMCs can be in communication with theDCMC.

In a particular embodiment, the RMCs operate to provide an InternetProtocol-based (IP) keyboard-video-mouse (KVM), an Ethernet managementswitch (EMS), and a serial aggregator. Moreover, the RMCs operate toprovide a U-space aligned description of the equipment in the serverrack. Here, the U-space alignment is determined based upon a managementconnection between the RMC and the equipment, or based upon a powerconnection between a power distribution unit (PDU) and the equipment. Inanother embodiment, the RMCs operate to provide a common real-time clockfunction for the equipment in the server rack, and to provide othercommon functions of the equipment in the server rack. In anotherembodiment the RMCs operate to provide virtual local area network (vLAN)mapping for the equipment in the server rack. In a first case, the vLANmapping is provided based upon the location of a management connectionbetween the RMC and the equipment. In another case, the vLAN mapping isprovided based upon the location of a power connection between the PDUand the equipment. In another embodiment, a power map of the data centeris obtained based upon the location of a power connection between theRMC and the PDU.

In another embodiment, the data center operates to providepreemptive/proactive cooling of the equipment in the server racks on aper rack basis and on a data center wide basis. Further, one or more ofthe tile and the server racks operate to provide closed loop thermalcontrol. In a first case, a floor tile operates to control whether ornot air is permitted to flow through the vent of the floor tile. Inanother embodiment, an air flow based power generator is provided forthe floor tiles, in order to provide power for the TMC.

In another embodiment, one or more of the floor tiles and the serverracks operate to determine the weight of the server rack and tocalculate weight related parameters, such as safety margins, for theserver rack. In a particular embodiment, the leveling feet of the serverracks operate to determine the weight of the rack. In yet anotherembodiment, the leveling feet of the server racks are automaticallycontrolled to provide leveling of the server racks. In anotherembodiment, the RMCs operate to determine when a server rack is topheavy, for example, when several pieces of equipment have been removedfrom the bottom of a server rack and other equipment has been left inplace in the top of the server rack. Here, the RMCs operate to providean interlock to keep service personnel from removing the equipment fromthe top of the rack. In another embodiment, the RMCs operate to detectwhen a side panel of the server rack has been removed or a ground is notconnected.

FIG. 2 illustrates an embodiment of a floor 200 similar to floor 130,that includes passive floor tiles 202, 204, 206, 208, 210, 212, 214,216, and 218. Floor tiles 202, 204, and 206 are illustrated as includingradio frequency identification (RFID) tags 203, 205, and 207,respectively, RFID tags 203, 205, and 207 operate to store informationrelated to the location of the associated floor tiles 202, 204, and 206,and to permit the communication of the information via a radio-frequencyelectromagnetic fields. The information stored in RFID tag 203 includesa grid location on floor 200 that identifies floor tile 202, a weightlimit for server racks and equipment located on the floor tile, a rangeof IP addresses for the equipment, a client name associated with theequipment, and a system name for the equipment. RFID tags 205 and 207include similar information to RFID tag 203. Floor tiles 208-218 eachinclude RFID tags that are similar to RFID tags 203, 205, and 207, andthat include information related to each floor tile's location, weightlimit, and equipment identification. The skilled artisan will recognizethat the information included in RFD tags 203, 205, and 207, asdescribed above, is exemplary, and that other information can be storedin an RFID tag, as needed or desired. For example, an RFID tag locatedon a floor tile can include network routing information associated withthe equipment located on the floor tile, such as VLAN mappings, networksub-masks, and the like, asset information such as a model number and aserial number for the floor tile, or other information, as needed ordesired.

RFID tags 203, 205, and 207 are activated by a magnetic field created byan RFID tag reader, and provide the stored information via radio wavesthat are received by the RFID tag reader. In a particular embodiment,RFID tags 203, 205, and 207 are passive devices that receive operatingpower from the magnetic field. In another embodiment, RFID tags 203,205, and 207 are active devices that are activated by the magneticfield, but, that include a power source, such as a battery, to generatethe radio waves to provide the stored information to the RFID reader. Ineither case, REID tags 203, 205, and 207 can be provided in the form ofadhesive stickers that are applied to the respective floor tiles 202,204, and 206, or the RFID tags can be embedded in the respective floortiles, as needed or desired. Further, RFID tags 203, 205, and 207 can bepre-programmed with the information prior to delivery to a data center,or the RFID tags can be programmed at the data center.

In a particular embodiment, floor tiles 202-218 can include near-fieldcommunication (NFC) devices in the place of the REID tags. Here, the NFCdevices can store information similar to the information stored in theRFID tags. However, here, the NFC devices can be configured such thatthe stored information is rewriteable. In this way, floor tiles 202-218can be mass produced and programmed with the desired information at thedata center, and can also be reprogrammed if the needs of the datacenter change, or if a particular floor tile needs to be replaced. Theskilled artisan will recognize that, in certain situations, not allfloor tiles of a floor will need to include an RFID tag or a NFC device.For example, in a common configuration, one server rack is located ontwo floor tiles, and multiple floor tiles may be provided as walkwayspace in front of and in back of the server racks. Here, only one of thefloor tiles under each server rack would need to include locationinformation, and the other floor tiles under the server racks and thefloor tiles in the aisles would not need to include RFID tags or NFCdevices. The skilled artisan will recognize that other passive devicescan be utilized to perform the functions of the RFID tags as disclosedherein, as needed or desired. Further, the skilled artisan willrecognize that devices other than REID tags can be utilized, such asanother memory device, as needed or desired. In a particular embodiment,RFID tags 203, 205, and 207 include a subset of the information, such asa grid location and a pointer to a remote storage device, from which thecomplete information can be retrieved.

FIG. 3 illustrates a portion of floor 200 of FIG. 2, including floortiles 202 and 204. A server rack 310 is located on floor tile 202, and aserver rack 320 is located on floor tile 204. Server rack 310 includesan RFID tag reader 312, and server rack 320 includes an RFID tag reader322. RFID tag 203 is activated by a magnetic field created by RFID tagreader 312, and provides the stored information via radio waves that arereceived by the RFID tag reader. Server rack 310 stores the information314 as described further, below. RFID tag 205 is activated by a magneticfield created by RFID tag reader 322, and provides the storedinformation to the RFID tag reader, and server rack 320 stores theinformation 324. In a particular embodiment, RFID tag readers 312 and322 are located proximate to the bottom of respective server racks 310and 320, in order to meet the range requirements of the RFID tags. Forexample, where an operating range for a particular REID standard may beless than one meter, REID tag readers 312 and 314 may be placed in thebottom of server racks 310 and 320, so as to be able to reliably readthe information from RFID tags 203 and 205. In the embodiment wherefloor tiles 202 and 204 include NFC devices in the place of the REIDtags, server racks 310 and 320 are provided instead with NFC readers. Inthis embodiment, the NFC reader in server rack 310 can establish apeer-to-peer (P2P) connection with the NFC device in floor tile 202, andthe NFC reader in server rack 320 can establish a P2P connection withthe NFC device in floor tile 204. In a particular embodiment, one ofserver racks 310 and 320 are removed from the data center, and a newserver rack is located on the empty floor tile 202 or 204. When the newserver rack is installed in the data center, the new server rack obtainsthe location information from the floor tile. In this way, the newserver rack can be configured similarly to the server rack that wasremoved. The skilled artisan will recognize that RFID tags 203, 205, and207 can be written to, in order to change or reconfigure the informationincluded in the RFID tags.

FIG. 4 illustrates an embodiment of an active floor tile 400 including atile management controller (TMC) 410, a communication module 420, amemory 430, one or more sensors 440, and a power source 450. TMC 410represents a service processor that is connected to communication module420, memory 430, sensors 440, and power source 450, and operates toprovide intelligence to floor tile 400 to gather, process, and storeinformation 432 related to the location and operation of the floor tile,and to permit the communication of the information. Information 432 isstored in memory 430 and includes a grid location of floor tile 400 on afloor that identifies the floor tile, a weight limit for server racksand equipment located on the floor tile, a range of IP addresses for theequipment, a client name associated with the equipment, and a systemname for the equipment. Information 432 can also include otherinformation, such as network routing information associated with theequipment located on floor tile 400, such as VLAN mappings, networksub-masks, and the like, asset information such as a model number and aserial number for the floor tile, climate information such as thetemperature and humidity above or below the floor tile or elsewhere inthe data center, climate settings for active cooling or heating,described further below, or other information, as needed or desired. Ina particular embodiment, TMC 410 is connected to a management networkthat includes other service processors of the equipment and the serverrack and a management system associated with the data center. In aparticular embodiment, TMC 410 operates in accordance with anIntelligent Platform Management Interface (IPMI) functionalimplementation. Memory 430 represents a data storage device such as anon-volatile random access memory (NVRAM) or another data storagedevice.

Communication module 420 includes a communication port 422 that isoperable to provide communications outside of floor tile 400. Inparticular, communication port 422 can be connected to a server rack toprovide information 432 to the server rack. In addition, the server rackcan direct TMC 410 to update or modify the contents of information 432.For example, if a server rack located on floor tile 400 is reconfiguredto have a different range of IP addresses, the server rack can directTMC 410 to update the IP address ranges in information 432. In this way,if the server rack is removed and a new server rack is located in itsplace, floor tile 400 includes the updated server rack configurationinformation which can be uploaded to the new server rack. Further, amanufacturer of floor tile, 400 can use communication port 422 topre-program information 432 on the floor tile, in accordance with acustomer request, and the floor tile can be supplied to a data centerwith the configuration information already in place, thereby speedingthe installation of the server rack located at the floor tile. anotherembodiment, floor tile 400 is received in an unconfigured state, andinformation 432 is provided at the time of installation. An example ofcommunication port 422 includes a wired communication port, such as anRS-232 port, an Ethernet port, a Universal Serial Bus (USB) port, anIEEE 1394 (Firewire) port, a Controller Area Network (CAN) port, anInter-Integrated Circuit (I2C) port, a Serial Peripheral interface (SPI)port, or another wired communication port, a wireless communicationport, such as an NFC port, an IEEE 803.11 (WiFi) port, a Bluetooth port,or another wireless communication port, or a combination thereof.

In a particular embodiment, described fully below, floor tile 400operates to communicate with one or more adjacent floor tiles. In thisembodiment, communication module 410 operates to provide communicationto both the server rack and the adjacent floor tiles via communicationport 422. In another case, communication module 410 includes one or moreadditional communication ports similar to communication port 422. Here,communication port 422 can be dedicated to the communication between TMC410 and the server rack, and the additional communication port can bededicated to communication between the TMC and the one or more adjacentfloor tiles.

Sensors 440 operate to provide TMC 410 with information related to theenvironment surrounding floor tile 400. For example, sensors 440 caninclude temperature and humidity sensors on the top side and the bottomside of floor tile 400, and TMC 410 can provide the temperature andhumidity information to a server rack or to a DCMC to provide accurate,localized feedback as to the performance of an AC system in the datacenter. In another example, sensors 440 can include a strain gage orother weight sensor to measure the weight of a server rack that islocated on floor tile 400, and TMC 410 can provide the weightinformation to the server rack or the DCMC to provide a warning that theserver rack is over loaded. Power source 450 represents a source ofpower for operating TMC 410, communication module 420, memory 430, andsensors 440. An example of power source 450 includes an off-tile powersource, such as a plug in power connection to an AC power supply, a DCpower supply, a Power-Over-Ethernet source, or another power connection,an on-tile power source such as a battery or generator, or a combinationthereof. In a particular embodiment, information 432 includes a subsetof the information, such as a grid location and a pointer to a remotestorage device, from which the complete information can be retrieved.

FIG. 5 illustrates an embodiment of a data center floor 500 includingactive floor tiles 502, 504, 506, 508, 510, 512, 514, 516, and 518, anda DCMC 520. Active floor tiles 502-518 are similar to active floor tile400 and each includes a TMC and a communication port that is connectedto DCMC 520. As such, active floor tiles 502-518 operate to gather,process, and store information related to the location and operation ofthe floor tiles, and to permit the communication of the information withDCMC 520. The communication ports represent wired connections such as anRS-232 port, an Ethernet port, a USB port, a Firewire port, a CAN port,an I2C port, a SPI port, or another wired communication port, as neededor desired. Here, DCMC 520 operates to direct the TMCs to store, update,or modify the information stored on active floor tiles 502-518. In aparticular embodiment, because active floor tiles 502-518 are connectedto DCMC 520 via a wired connection, the active floor tiles can receivethe information based upon the wired connection that is provided to theDCMC. In particular, each of active floor tiles 502-518 can include aunique identification such as a media access control (MAC) address, anInternet Protocol (IP) address, a globally unique identification (GUID),or another unique identification, and DCMC 520 can send uniqueinformation to each of the active floor tiles based upon the uniqueidentification and a known mapping of the connections to the activefloor tiles. For example, DCMC 520 can know that an active floor tilethat is connected to a port that is located in the lower left-handcorner of floor 500 has a grid coordinate of (1,A), and then can sendinformation unique to that location to any active floor tile that isconnected to that port. In this way, any active floor tile can bereplaced, and DCMC 520 will automatically update the replacement activefloor tile with the information that is unique to the location. In aparticular embodiment, each TMC can communicate with a server rackmanagement controller of a server rack that is located on respectivefloor tiles 502-518, as described further below.

FIG. 6 illustrates an embodiment of a data center floor 600 includingactive floor tiles 602, 604, 606, 608 610, 612, 614, 616 and 618, and aDCMC 620. Floor 600 is similar to floor 500, except that active floortiles 602-618 each include a wireless communication port, such as an NFCport, an IEEE 803.11 (WiFi) port, a Bluetooth port, or another wirelesscommunication port, and each of the active floor tiles includes a uniqueidentification. As such, DCMC 620 can communicate wirelessly with theactive floor tiles to direct the TMCs to store, update, or modify uniqueinformation for each of the active floor tiles. In a particularembodiment, each TMC can communicate with a server rack managementcontroller of a server rack that is located on respective floor tiles602-618, as described further below.

FIG. 7 illustrates an embodiment of a data center floor 700 includingactive floor tiles 702, 704, 706, 708 710, 712, 714, 716, and 718, and aDCMC 720. Floor 700 is similar to floor 500 and active floor tiles702-718 are similar to active floor tile 400, including a TMC and acommunication port. As such, active floor tiles 702-718 operate togather, process, and store information related to the location andoperation of the floor tiles, and to permit the communication of theinformation with DCMC 720. The communication ports represent wiredconnections. Here, only active floor tile 702 is directly connected toDCMC 720. However, each of active floor tiles 702-718 have acommunication port on each edge of the active floor tiles, such that twoadjacent active floor tiles are connected to each other. In a particularembodiment, because active floor tiles 702-718 are connected to eachother and to DCMC 720, the active floor tiles can receive theinformation from the DCMC or the RMC. In particular, each of activefloor tiles 702-718 can include a unique identification, and DCMC 520can send unique information to each of the active floor tiles based uponthe unique identification and a known mapping of the connections to theactive floor tiles. For example, DCMC 520 can know that an active floortile that is directly connected is located in the lower left-hand cornerof floor 700, and has a grid coordinate of (1,A). Here DCMC 720 candirect active floor tiles 702-718 to perform a discovery of each activefloor tile's neighbors and thereby create a map of floor 700, and thencan send information unique to each location based upon the map.Further, DCMC 720 can derive a map of the physical locations of theserver racks in the data center and the equipment in the server racks,and provide a graphical representation of the locations. In this way,any active floor tile can be replaced, and DCMC 720 will automaticallyupdate the replacement active floor tile with the information that isunique to the location. In a particular embodiment, each TMC cancommunicate with a server rack management controller of a server rackthat is located on respective floor tiles 702-718, as described furtherbelow.

FIG. 8 illustrates an embodiment of a data center floor 800 includingactive floor tiles 802, 804, 806, 808, 810, 812, 814, 816, and 818, anda DCMC 820. Floor 800 is similar to floor 700, except that active floortiles 802-818 each include a wireless communication port, such as an NFCport, an IEEE 803.11 (WiFi) port, a Bluetooth port, or another wirelesscommunication port, such that DCMC 820 can communicate wirelessly withthe active floor tiles. Active floor tiles 802-818 can be directed toperform a discovery of each active floor tile's neighbors and therebycreate a map of floor 800, and DCMC 820 can send information unique toeach location based upon the map. In a particular embodiment, each TMCcan communicate with a server rack management controller of a serverrack that is located on respective floor tiles 802-818, as describedfurther below.

FIG. 9 illustrates an embodiment of a server rack 900 including a rackmanagement controller (RMC) 910, a communication module 920, a memory930, and one or more sensors 940. RMC 910 represents a service processorthat is connected to communication module 920, memory 930, and sensors940, and operates to provide intelligence to server rack 900 to gather,process, and store information 932 related to the location and operationof the server rack and the equipment in the server rack, and to permitthe communication of the information. Information 932 is stored inmemory 930 and includes a grid location on a floor of a datacenter thatserver rack 900 is located, a weight limit for the server rack andequipment, a range of IP addresses for the equipment, a client nameassociated with the equipment, and a system name for the equipment.Information 932 can also include other information, such as networkrouting information associated with the equipment in server rack 900,such as network port and VLAN mappings, network sub-masks, and the like,asset information such as a model number and a serial number for thefloor tile, climate information such as the temperature and humidityabove or below the server rack, climate settings for active cooling orheating, described further below, or other information, as needed ordesired. In a particular embodiment, RMC 910 is connected to amanagement network that includes other service processors of theequipment in server rack 900 and a management system associated with thedata center. In a particular embodiment, RMC 910 operates in accordancewith an IPMI functional implementation. Memory 930 represents a datastorage device such as a non-volatile random access memory (NVRAM) oranother data storage device.

Communication module 920 includes a communication port 922 that isoperable to provide communications outside of server rack 900. Inparticular, communication port 922 can be connected to an active floortile such as active floor tile 400 to provide information 932 to theactive floor tile. In addition, the active floor tile can direct RMC 910to update or modify the contents of information 932 and to modify theconfigurations of the equipment in server rack 900. For example, ifserver rack 900 is reconfigured to have a different range of IPaddresses, the server rack can direct the active floor tile to updatethe IP address ranges in the information stored therein. In this way, ifserver rack 900 is removed and a new server rack is located in itsplace, the active floor tile includes the updated server rackconfiguration information which can be uploaded to the new server rack.Further, a manufacturer of server rack 900 can use communication port922 to pre-program information 932 on the server rack, in accordancewith a customer request, and the server rack can be supplied to a datacenter with the configuration information already in place, therebyspeeding the installation of the server rack. In another embodiment,server rack 900 is received in an unconfigured state, and information932 is provided at the time of installation. An example of communicationport 922 includes a wired communication port, such as an RS-232 port, anEthernet port, USB port, a Firewire port, a CAN port, an I2C port, a SPIport, or another wired. communication port, a wireless communicationport, such as an NFC port, a WiFi port, a Bluetooth port, or anotherwireless communication port, or a combination thereof.

Sensors 940 operate to provide RMC 910 with information related to theenvironment surrounding server rack 900 and of the data center. Forexample, sensors 940 can include temperature and humidity sensors on thetop side and the bottom side of server rack 900, and RMC 910 can providethe temperature and humidity information to an active floor tile or to aDCMC to provide accurate, localized feedback as to the performance of anAC system in the data center. In another example, sensors 940 caninclude a strain gage or other weight sensor to measure the weight ofserver rack 900, and RMC 910 can provide the weight information to DCMCto provide a warning that the server rack is over loaded. For example, astatic weight capacity can be exceeded, a location/floor weight capacitycan be exceeded, or a server rack dynamic weight capacity can beexceeded.

In a particular embodiment, RMC 910 operates to provide a managementaccess point for the equipment in server rack 900, such that the RMC canmanage the service processor functions for the entire server rack, Forexample, RMC 910 can provide for the management of the sensor data andpower functions of the servers and chassis that are installed in serverrack 900, manage the inventory of the server rack, monitor equipmenthardware, operating software and environmental statuses in the serversand chassis, provide lifecycle management and firmware updates, or otherservice processor functions, as needed or desired. In another case, RMC910 also operates as a management access point for passive and activefloor tiles upon which server rack 900 is located. In anotherembodiment, RMC 900 operates to aggregate the management functions ofother similar server racks, providing a centralized access point betweenthe other server racks and the data center management system.

FIG. 10 illustrates an embodiment of a data center 1000 including anactive floor tile 1010 and a server rack 1020. Active floor tile 1010 issimilar to active floor tile 400, and includes a TMC 1022, acommunication module 1024, a memory 1026, and one or more sensors 1028.Server rack 1020 is similar to server rack 900, and includes a RMC 1022,a communication module 1024, a memory 1026, and one or more sensors1028. Here, memory 1016 includes tile information 1017 similar toinformation 432 in memory 430 of active floor tile 400. When server rack1020 is installed on active floor tile 1010, a wired connection 1030 isprovided between communication module 1014 and communication module1024. Tile information 1017 is then provided to RMC 1022 for storage inmemory 1026 as server rack information 1027. In a particular embodiment,tile information 1017 includes configuration information for theequipment in server rack 1020, that can be implemented via theequipment's service processor network, such as a BMC, an iDRAC, oranother service processor. In this way, the operations of server rack1020 are tethered to the location of active floor tile 1010. An exampleof wired connection 1030 includes an RS-232 port, an Ethernet port, aUSB port, a Firewire port, a CAN port, an I2C port, a SPI port, anotherwired communication port, or a combination thereof. In anotherembodiment, communication module 1014 includes a wireless communicationport 1015 and communication module 1024 includes a wirelesscommunication port 1025, and when server rack 1020 is installed onactive floor tile 1010, a wireless connection 1040 is provided betweencommunication module 1014 and communication module 1024. An example ofwireless connection 1040 includes an NFC port, a WiFi port, a Bluetoothport, a other wireless communication port, or a combination thereof.

FIGS. 11 and 12 illustrate an embodiment of a server rack 1100 includinga rack space 1110, and a RMC 1130 with an IP Keyboard/Video/Mouse(KVM)-Ethernet Management Switch-Serial Aggregator 1140, hereinafter“aggregator 1140.” Rack space 1110 represents a standard server rack,such as a 19-inch rack equipment mounting frame or a 23-inch rackequipment mounting frame, and includes rack units 1112, 1114, 1116,1118, 1120, and 1122. Rack units 1112-1122 represent special divisionsof rack space 1110 that are a standardized unit of 1.75 inches high. Forexample, a piece of equipment that will fit an one of rack units1112-1122 shall herein be referred to as a 1-U piece of equipment,another piece of equipment that takes up two of the rack units iscommonly referred to as a 2-U piece of equipment, and so forth. As such,rack units 1112-1122 are numbered sequentially from the bottom to thetop as 1U, 2U, 3U, 4U, 5U, and 6U. The skilled artisan will recognizethat other configurations for rack units 1112-1122 can be utilized asneeded or desired. For example, a rack unit can be defined by theElectronic Components Industry Association standards council.

Server rack 1100 is similar to server rack 900, and thus RMC 1130 isconnected to a communication module, a memory, and one or more sensors(not illustrated) of server rack 1100. Aggregator 1140 includes thefunctions of an IP KVM that permits the remote access to the keyboard,video, and mouse functions of the equipment that is installed in serverrack 1100. For example, a remote operator can access the keyboard,video, and mouse functions of a server that is installed in server rack1100 by addressing IP packets to the Ethernet port of the server. Theskilled artisan will recognize that other network protocols can be usedto access the keyboard, video, and mouse functions of the equipment thatis installed in server rack 1100, as needed or desired. Aggregator 1140also includes the functions of a Ethernet management switch thatestablishes a management network between the service processors of theequipment installed in server rack 1100, and a management system of thedata center. Aggregator 1140 also includes the functions of an I/Oaggregator for stand-atone servers installed in server rack 1100. Assuch, aggregator 1140 integrates separate functions that would otherwiseconsume rack space 1110 into a separate unit that can be located in thetop, the bottom, or the sides of server rack 1100. As illustrated,aggregator 1140 is included as an element of RMC 1130, but thisimplementation is only exemplary, and the functions of RMC 1130 andaggregator 1140 can be integrated into other devices as needed ordesired. For example, an Ethernet management switch can be embodiedwhich includes the functions of an IP KVM, an I/O aggregator, and a RMC,an IP KVM can be embodied to include the functions of an Ethernetmanagement switch, and I/O aggregator, and a RMC, or another combinationcan be embodied, as needed or desired.

Aggregator 1140 is connected to a service port 1142 associated with rackunit 1112, a service port 1144 associated with rack unit 1114, a serviceport 1146 associated with rack unit 1116, a service port 1148 associatedwith rack unit 1118, a service port 1150 associated with rack unit 1120,and a service port 1152 associated with rack unit 1122. For the purposesof this disclosure, a service port represents a data communication linkthat provides for a connection to one or more service processors on amanagement network of the data center. For example service ports1142-1152 provide a connection to RMC 1130 and equipment that isconnected to one of the service ports forms a node on the managementnetwork.

Aggregator 1140 operates to distinguish between equipment that isconnected to a first service port 1142, 1144, 1146, 1148, 1150, or 1152,and equipment that is connected to a second service port. In aparticular embodiment, aggregator 1140 distinguishes between serviceports because each service port is connected to a unique port of theaggregator. For example, utilizing the Ethernet management switchfunction of aggregator 1140, each of service ports 1142-1152 can beconnected to a port of the aggregator that is uniquely associated withrespective rack units 1112-1122, but this is not necessarily so, and theskilled artisan will recognize that other schemes for associating theservice ports with the rack units can be utilized, as needed or desired.In a particular embodiment, service ports 1142-1152 are collocatedphysically with the associated rack units 1112-1122, as illustrated. Inthis embodiment, RMC 1130, aggregator 1140 and service ports 1142-1152can be integrated into a single field replaceable unit (FRU) that isinstalled along the side of server rack 1100, such that the inclusion ofthe RMC, the aggregator, and the service ports does not necessitate anincrease in the height of the server rack. For example, as describedmore fully below, RMC 1130, aggregator 1140 and service ports 1142-1152can be integrated with a power distribution unit (PDU) of server rack1100. The skilled artisan will recognize that rack units 1112-1122 canbe ordered from the bottom of server rack 1130 to the top of the serverrack, or can be ordered from the bottom of the server rack to the top ofthe server rack, as needed or desired.

FIG. 12 illustrates server rack 1100 wherein rack space 1110 ispopulated with two 2-U servers 1160 and 1170, and with two 1-U servers1180 and 1190. 2-U server 1160 is installed in rack spaces 1112 and1114, 2-U server 1170 is installed in rack spaces 1116 and 1118, 1-Userver 1180 is installed in rack space 1120, and 1-U server 1190 isinstalled in rack space 1122, 2-U server 1160 includes a service port1162, 2-U server 1170 includes a service port 1172, 1-U server 1180includes a service port 1182, and 1-U server 1190 includes a serviceport 1192. As illustrated, service port 1162 is connected to serviceport 1142 via a connector cable 1164, service port 1172 is connected toservice port 1146 via a connector cable 1174, service port 1182 isconnected to service port 1150 via a connector cable 1184, and serviceport 1192 is connected to service port 1152 via a connector cable 1194.Service ports 1162, 1172, 1182 and 1192 are each connected to arespective service processor (not illustrated) that comprises a node onthe management network provided by RMC 1130.

Note that, because aggregator 1140 operates to distinguish betweenequipment that is connected to service ports 1142-1152, RMC 1130 isoperable to identify that 2-U server 1160 is connected at rack space1112, that 2-U server 1170 is connected at rack space 1116, that 1-Userver 1180 is connected at rack space 1120, and that 1-U server 1190 isconnected at rack space 1122. In a particular embodiment, connectorcables 1164, 1174, 1184, and 1194 are custom made such that they canonly reach between one of service ports 1142-1152 a service port on apiece of equipment that is adjacent to the respective rack spaces 1112,1114, 1116, 1118, 1120, and 1122. Thus, for example, connector cable1184 is unable to span between service port 1150 and either serviceports 1172 or 1192. In this way, not only are servers 1160, 1170, 1180,and 1190 uniquely associated with respective service ports 1142, 1146,1150, and 1152, but also, the servers are identified as being physicallylocated in respective rack spaces 1112, 1116, 1120, and 1122. Further,in a situation where 2-U servers 1160 and 1170 identify themselves toRMC 1130 as being 2-U pieces of equipment, then 2-U server 1160 is alsoidentified as being physically located in rack spaces 1112 and 1114, and2-U server 1170 is identified as being physically located in rack spaces1116 and 1118. Even in an embodiment where connector cables 1164, 1174,1184, and 1194 are general purpose cables that can reach between any oneof service ports 1142, 1144, 1146, 1148, 1150, and 1152 and a serviceport on any piece of equipment installed in server rack 1100, thebenefit of identifying the physical location of each piece of equipmentis achieved by simply connecting each piece of equipment to the serviceport 1142-1152 that is most closely associated with the piece ofequipment.

In a particular embodiment, RMC 1130 provides a map of the physicallocations of the equipment installed in server rack 1100 to a DCMC.Here, the DCMC operates to receive such location maps from each serverrack in a data center, and creates a map of the physical locations ofall of the equipment in the data center. In this way, when there is aproblem with a particular piece of equipment, a service technician canbe provided information that identifies the server rack that includesthe piece of equipment, and the location within the server rack,eliminating the time-consuming process of tracking down the piece ofequipment by hand. In a particular embodiment, a piece of equipment thatis a multi-rack-unit piece of equipment can have a service port locatedproximate to other than a bottom rack unit. For example, a 2-U servercan have a service port that is located proximate to a top of theserver, a 3-U server can have a service port that is located proximateto a middle of the server, or another configuration for the service portcan be provided by a server. Here, aggregator 1140 operates to determinethe location of the equipment based upon information provided by theserver as to the location of the service port in the equipment. Inanother embodiment, where apiece of equipment is a multi-rack-unit pieceof equipment, the service port on the piece of equipment can beconnected. to the service port of the server rack that is associatedwith the top rack unit of the piece of equipment, and RMC 1130 operatesto locate the piece of equipment based upon the connection. In thisembodiment, the choice of connection to the service port associated withthe top rack unit or to the service port associated with the bottom rackunit is user selectable. For example, service port 1162 can be connectedto service port 1144, and service port 1172 can be connected to serviceport 1148, as illustrated by connectors 1166 and 1176, respectively

FIG. 13 illustrates an embodiment of a server rack 1300 similar toserver rack 1100 and including a RMC 1330 with a real time clock 1340,and RMC 1330 is connected to a communication module, a memory, and oneor more sensors (not illustrated) of the server rack. Real time clock1340 is connected to a service port 1342 associated with a rack unit 1U,a service port 1344 associated with a rack unit 2U, a service port 1346associated with a rack unit 3U, a service port 1348 associated with arack unit 4U, a service port 1350 associated with a rack unit 5U, and aservice port 1352 associated with a rack unit 6U. Server rack 1300 ispopulated with two 2-U servers 1360 and 1370, and with two 1-U servers1380 and 1390. 2-U server 1360 includes a service port 1362 that isconnected to service port 1342, 2-U server 1370 includes a service port1372 that is connected to service port 1346, 1-U server 1380 includes aservice port 1382 that is connected to service port 1350, and 1-U server1390 includes a service port 1392 that is connected to service port1352. Service ports 1362, 1372, 1382 and 1392 are each connected to arespective service processor (not illustrated) that comprises a node onthe management network provided by RMC 1330.

Real time clock 1340 operates to provide a consistent time base forserver rack 1300. In a particular embodiment, real time clock 1340includes a battery operable to maintain power to a clock circuit thatmaintains an accurate time stamp. For example, real time clock 1340 canoperate to provide an accuracy of 2 to 3 seconds per day. Additionally,RMC 1220 operates to make periodic contact with a time-base service suchas an atomic clock system that provides a Network Time Protocol (NTP)based synchronized timestamp to maintain the accuracy of real time clock1340. For example, using the NTP timestamp, real time clock 1340 canmaintain an accuracy of better than one millisecond. Moreover, bycoordinating real time clocks in other server racks of the data center,the entire data center can maintain a similar accuracy.

In a particular embodiment, servers 1360, 1370, 1380, and 1390 operateto obtain the timestamp from real time clock 1340, such that the serversalso maintain a high degree of accuracy. Moreover, because servers 1360,1370, 1380, and 1390 obtain the timestamp from real time clock 1340, theservers do not include their own separate real time clock functions,thereby saving on the cost of the components to provide the real timeclock function, and also saving space on the motherboards of theservers. In another embodiment, RMC 1310 also represents other sharedfunctions for servers 1360, 1370, 1380, and 1390. For example, RMC 1310can include warning or critical status handlers for servers 1360, 1370,1380, and 1390, log handlers for the servers, housekeeping informationfor the servers, and the like.

FIG. 14 illustrates an embodiment of a server rack 1400 similar toserver rack 1100 and including a RMC 1430 with a vLAN setup module 1440,and a rack switch 1450, and RMC 1430 is connected to a communicationmodule, a memory, and one or more sensors (not illustrated) of theserver rack. vLAN setup module 1440 is connected to a service port 1442associated with a rack unit 1U, a service port 1443 associated with arack unit 2U, a service port 1444 associated with a rack unit 3U, aservice port 1445 associated with a rack unit 4U, a service port 1446associated with a rack unit 5U, and a service port 1447 associated witha rack unit 6U. Server rack 1400 is populated with two 2-U servers 1460and 1470, and with two 1-U servers 1480 and 1490. 2-U server 1460includes a service port 1462 that is connected to service port 1442, 2-Userver 1470 includes a service port 1472 that is connected to serviceport 1444, 1-U server 1480 includes a service port 1482 that isconnected to service port 1446, and 1-U server 1490 includes a serviceport 1492 that is connected to service port 1447. Service ports 1462,1472, 1482 and 1492 are each connected to a respective service processor(not illustrated) that comprises a node on the management networkprovided by RMC 1430.

Rack switch 1450 includes a host port 1452 connected to a host port 1466of server 1460, a host port 1454 connected to a host port 1476 of server1470, a host port 1456 connected to a host port 1486 of server 1480, ahost port 1458 connected to a host port 1496 of server 1490, and aservice port. 1459 connected to a service port 1432 of RMC 1430. For thepurposes of this disclosure, a host port represents a data communicationlink that provides a connection between one or more host processors on aserver to a primary network of the data center. For example host ports1452-1458 provide a connection for servers 1460, 1470, 1480, and 1490 tohave access to a network backbone or other server racks on the primarynetwork of the data center.

In a particular embodiment, RMC 1430 operates to detect, based upon thephysical location within server rack 1400 of the servers 1460, 1470,1480, and 1490, which host port 1452 1454, 1456, or 1458 is connected towhich server. Here, RMC 1430 communicates via the management network toservice processors of servers 1460, 1470, 1480, and 1490, and receivesinformation related to the identifications of the respective host ports1466, 1476, 1486, and 1496. For example, RMC 1430 can receive the MACaddresses of host ports 1466, 1476, 1486, and 1496, the IP addresses ofthe host ports, or other information that identifies the host ports.Further, RMC 1430 communicates via the management network to a serviceprocessor of rack switch 1450 and receives information related to whichof host ports 1452-1458 are connected to the particular identified hostports 1466, 1476,1486, and 1496 (i.e., to which particular MAC or IPaddress). In this way, RMC 1430 provides a physical port map of theconnections on server rack 1400. Further, RMC 1430 operates to providethe port map to a DCMC of the data center, and the DCMC combines theport map with other similar port maps received from the other serverracks to provide a physical port map of the connections within the datacenter.

In a particular embodiment, vLAN setup module 1440 operates todetermine, via the management network to service processors of servers1460, 1470, 1480, and 1480, whether or not one or more of the serversare provisioned for any vLANs. For example, one or more of servers 1460,1470, 1480, and 1490 can provide a virtualized operating environmentthat can establish a separate vLAN for each virtual machine that isinstantiated on the server. Then, based upon the connection map, vLANsetup module 1440 directs, via the management network to a serviceprocessor of rack switch 1450, the rack switch to configure host ports1452-1458 for the detected vLANs. Further, vLAN setup module 1440operate to communicate via the management network to the DCMC and toother server racks, the configuration information for the vLANs, suchthat other network switching devices in the data center can beconfigured for the detected vLANs. In a particular embodiment, vLANsetup module 1440 operates to detect when a new vLAN is established andto automatically configure the backbone of the data center for the newlydetected vLAN.

In a particular embodiment, rack switch 1450 operates using aSpanning-Tree Protocol (STP) to prevent loops from being formed. Inaddition, RMC 1430 implements SPT to prevent loops when one or more ofservice ports 1442-1447 are utilized in a failover condition. Moreover,because RMC 1430 communicates directly with rack switch 1450 via serviceports 1432 and 1459, the RMC is in a position to detect when one of hostports 1452-1458 are operating in a loop, and to notify an administratorof the loop condition. Further, because RMC 1430 operates to create aport map of the host port connections on server rack 1400, loops can beproactively prevented, because the RMC can detect via the port map thatredundant paths are available, and can direct rack switch 1450 toeliminate redundant paths in the rack switch's routing tables, therebysuperseding the need of SPT operations to shut down host ports or therack switch.

FIG. 15 illustrates an embodiment of a server rack 1500 similar toserver rack 1100 and including a RMC 1530 with a power mapping module1540, and RMC 1530 is connected to a communication module, a memory, andone or more sensors (not illustrated) of the server rack. Power mappingmodule 1540 is connected to a power receptacle 1542 associated with arack unit 1U, a power receptacle 1544 associated with a rack unit 2U, apower receptacle 1546 associated with a rack unit 3U, a power receptacle1548 associated with a rack unit 4U, a power receptacle 1550 associatedwith a rack unit 5U, and a power receptacle 1552 associated with a rackunit 6U. Server rack 1500 is populated with two 2-U servers 1560 and1570, and with two 1-U servers 1580 and 1590. 2-U server 1560 includes apower receptacle 1562 that is connected to power receptacle 1542 via apower cord 1564, 2-U server 1570 includes a power receptacle 1572 thatis connected to power receptacle 1546 via a power cord 1574, 1-U server1580 includes a power receptacle 1582 that is connected to powerreceptacle 1550 via a power cord 1584, and 1-U server 1590 includes apower receptacle 1592 that is connected to power receptacle 1552 via apower cord 1594. Power receptacles 1562, 1572, 1582 and 1592 are eachconnected to a respective service processor (not illustrated) thatcomprises a node on the management network provided by RMC 1330.

Power mapping module 1540 operates to distinguish between equipment thatis connected to a first one of power receptacles 1542, 1544, 1546, 1548,1550, or 1552, and equipment that is connected to a second powerreceptacle. In particular, power mapping module 1540 can be coupled topower receptacles 1542-1552 to receive an indication when a power cordis plugged into a power receptacle. In a particular embodiment, powercords 1564, 1574, 1584, and 1594 are custom made such that they can onlyreach between one of power receptacles 1542, 1544, 1546, 1548, 1550, and1552 a power receptacle on a piece of equipment that is adjacent to therespective rack spaces. Thus, for example, power cord 1584 is unable tospan between power receptacle 1550 and either power receptacles 1572 or1592. In this way, not only are servers 1560, 1570, 1580, and 1590uniquely associated with respective power receptacles 1542, 1546, 1550,and 1552, but also, the servers are identified as being physicallylocated in the respective rack spaces. Even in an embodiment where powercords 1564, 1574, 1584, and 1594 are general purpose power cords thatcan reach between any one of power receptacles 1542, 1544, 1546, 1548,1550, and 1552 and a power receptacle on any piece of equipmentinstalled in server rack 1500, the benefit of identifying the physicallocation of each piece of equipment is achieved by simply connectingeach piece of equipment to the power receptacle 1542-1542 that is mostclosely associated with the piece of equipment. In a particularembodiment, more than one power receptacle is provided for each rackspace, such that, if a piece of equipment requires more power than thenumber of rack spaces that the piece of equipment occupies, the powercords to each power receptacle on the piece of equipment can still beplugged into the power receptacles associated with the occupied rackspaces. In another embodiment, multiple power receptacles are includedfor each rack space, and each power receptacle is associated with adifferent power whip of the data center. In this way, redundant powerand power balancing can be achieved while maintaining the benefits ofhaving the power receptacles associated with the rack spaces.

In a particular embodiment, RMC 1530 provides a map of the physicallocations of the equipment installed in server rack 1500 to a DCMC.Here, the DCMC operates to receive such location maps from each serverrack in a data center, and creates a map of the physical locations ofall of the equipment in the data center. In this way, when there is aproblem with a particular piece of equipment, a service technician canbe provided information that identifies the server rack that includesthe piece of equipment, and the location within the server rack,eliminating the time-consuming process of tracking down the piece ofequipment by hand. In a first case, power receptacles 1542-1552 includepower line communication modules (PLC) which permit the transmitting andreceiving of information from similarly equipped pieces of equipmentover the power cords that connect the pieces of equipment to the powerreceptacles. Here, power mapping module 1540 directs each powerreceptacle 1542, 1546, 1550, and 1552 to broadcast a power receptacleidentification to the respective servers 1560, 1570, 1580, and 1590, andthe servers in turn report the power receptacle identification to RMC1530 via the management network. In this way, RMC 1530 obtains the mapof the physical locations of the equipment installed in server rack1500. In a variation of the first case, power mapping module 1540provides a unique identifier to each power receptacle 1542, 1546, 1550,and 1552 to be broadcast the respective servers 1560, 1570, 1580, and1590, and the servers in turn report the unique identification to RMC1530 via the management network. In a second case, RMC 1530 broadcasts aunique identifier over the management network to each of servers 1560,1570, 1580, and 1590, and the servers each append their ownidentifications to the received unique identification and rebroadcastthe unique identifiers via respective power receptacles 1562, 1572,1582, and 1592 to the associated power receptacles 1542, 1546, 1550, and1552. RMC 1530 then receives the unique identifiers back from powerreceptacles 1542, 1546, 1550, and 1552 and obtains the map of thephysical locations of the equipment installed in server rack 1500.

In a particular embodiment, RMC 1530 operates to track the amount ofpower delivered by power receptacles 1542-1552 to the pieces ofequipment that are installed in server rack 1500. RMC 1530 alsomaintains power limits for each piece of equipment and for server rack1500 as a whole. Then, when RMC 1530 detects that a power limit has beenexceeded, the RMC can direct the equipment to take steps to reduce thepower consumption associated with the power limit. For example if one ofservers 1560, 1570, 1580, or 1590 is consuming more power than the limitset for the power consumption of that server, RMC 1530 can direct theserver to take steps to reduce the power consumption, such as tothrottle one or more processors of the server, reduce the I/O bandwidthof the server, or prioritize tasks that are being performed by theserver. In a case where a piece of equipment that is exceeding its powerlimit is operating a virtualized environment, RMC 1430 can direct thepiece of equipment to reduce the priority of a virtual machine that isdetermined to be consuming a large portion of the power. In anotherexample, if server rack 1500 is exceeding its power limit, then RMC 1530can take steps to reduce the running average power of the server rack bythrottling one or more of the pieces of equipment that are installed inthe server rack. The skilled artisan will recognize that the powerlevels can be tracked on a per-phase basis, and that the power levelscan be balanced per phase.

In another embodiment, RMC 1530 provides the power status of server rack1500 to the DCMC of the data center, and other similarly enabled serverracks provide their power status to the DCMC. Here, the DCMC operates tomanage the running average power of the data center as a whole. Forexample, if a particular server rack is consistently consuming too muchpower, the DCMC can direct the migration of one or more workloads to adifferent server rack that is consuming less power, or can direct theRMC to throttle one or more pieces of equipment that are installed inthe server rack.

In a particular embodiment, RMC 1530 operates to manage power standby ofthe equipment that is installed in server rack 1500. For example, wherea user of the data center provides a requirement for a number of serversto be placed in a standby (S5) state, RMC 1530 can monitor theutilization of servers 1560, 1570, 1580, and 1590, and determine that ausage threshold has been exceeded. In this case, RMC 1530 operates topower up one or more of servers 1560, 1570, 1580, or 1590 such that, ifthe usage continues to increase, the powered up server is already bootedand ready to be added to the user's needs. In another case, when theutilization decreases, RMC 1530 operates to power down one or more ofservers 1560, 1570, 1580, or 1590 to conserve power. In a particularembodiment, RMC 1530, power mapping module 1540, and power receptacles1542-1552 can be integrated with a PDU of server rack 1500.

FIG. 16 illustrates data center 100 of FIG. 1, where server racks112-120 include respective RMCs 11612-1620, floor tiles 132-140 includerespective TMCs 1632-1640, and respective vents 1652-1660, and DCMC 150includes a temperature control module 1670. Data center 100 operates tomanage AC in the data center to control provide temperature a controlledair flow, such as an exemplary air flow 1690, to the server racks112-120. Vents 1652-1660 permit the temperature controlled air to passfrom sub-floor 160 to cold aisle 170. There, the temperature controlledair is drawn through the equipment in server racks 112-120 to cool theequipment, and the air flows out the back of the server racks, removingthe heat from the equipment, and passing to hot aisle 180, where the hotair is recirculated through an AC system. In a particular embodiment,one or more of floor tiles 132-140 and server racks 112-120 operate toprovide closed loop thermal control for the equipment in the serverracks.

In a particular embodiment, described more filly with respect to FIG.17, below, a floor tile operates to control whether or not air ispermitted to flow through the vent of the floor tile. In anotherembodiment, described more fully with respect to FIG. 18, below, aserver rack operates to control air flow through the server rack. Inanother embodiment, one or more of RMCs 1612-1620, TMCs 1632-1640, andtemperature control module 1670 operates to provide preemptive/proactivecooling of the equipment in server racks 112-120 on a per rack basis andon a data center wide basis, as described more fully below. In anotherembodiment, described more fully with respect to FIG. 19, below, an airflow based power generator is provided for floor tile, in order toprovide power for the TMC.

FIG. 17 illustrates an embodiment of an active floor tile 1700, similarto active floor tile 400, including a TMC 1710, a communication module1720, a memory 1730, a temperature sensor 1742, a humidity sensor 1744,a power source 1750, and a vent 1760. Vent 1760 includes an actuator1762 and a baffle 1764. TMC 1710 represents a service processor that isconnected to communication module 1720, memory 1730, sensors 1742 and1744, power source 1750, and actuator 1762, and operates to provideintelligence to floor tile 1700 to gather, process, and storeinformation related to the location and operation of the floor tile, andto permit the communication of the information. The information inmemory 1730 includes climate information such as the temperature andhumidity above or below floor tile 1700, climate settings for activecooling or heating, described further below, or other information, asneeded or desired. In a particular embodiment, TMC 1710 is connected toa management network that includes other service processors of theequipment and the server rack and a management system associated withthe data center. In a particular embodiment, TMC 1710 operates inaccordance with an IPMI functional implementation. Memory 1730represents a data storage device such as a non-volatile random accessmemory (NVRAM) or another data storage device.

Communication module 1720 includes a communication port that is operableto provide communications outside of floor the 1700. In particular, thecommunication port can be connected to a server rack such as server rack1800, described below, to provide the information from memory 1730 tothe server rack. In addition, the server rack can direct TMC 1710 toupdate or modify the contents of the information. An example of thecommunication port includes a wired communication port, such as anRS-232 port, an Ethernet port, a USB port, a Firewire port, a CAN port,an I2C port, a SPI port, or another wired communication port, a wirelesscommunication port, such as an NFC port, a WiFi port, a Bluetooth port,or another wireless communication port, or a combination thereof.

Sensors 1742 and 1744 operate to provide TMC 1710 with informationrelated to the environment surrounding floor tile 1700. For example,sensors 1742 and 1744 can be located on the top side of floor tile 1700,on the bottom side of the floor tile, or on both the top side and thebottom side, and TMC 1710 can provide the temperature and humidityinformation to a server rack or to a DCMC to provide accurate, localizedfeedback as to the performance of an AC system in the data center. Inanother embodiment, sensors 1742 and 1744 can be remote from floor tile1700, and the information from the sensors can be received viacommunication module 1720.

Vent 1760 permits air flow 1770 of thermally controlled air from a datacenter AC system to pass from the bottom side of floor tile 1700 to thetop side of the floor tile, to permit the thermally controlled air topass to the equipment in server racks proximate to the floor tile. Aportion 1772 of air flow 1770 passes next to sensors 1742 and 1744, andthe sensors obtain a measurement of the temperature and humidity,respectively of the air flow. TMC 1710 operates to determine if theenvironment surrounding floor tile 1700 is such to necessitate thesupply of more or less of air flow 1770 to the equipment in the serverracks proximate to the floor tile, and to direct actuator 1762 toposition baffle 1764 to restrict more or less of the air flow, asdictated by the environment surrounding the floor tile. In a particularembodiment, floor tile 1700 includes one or more additional sensors,such as pressure sensors, mass air flow sensors, and air flow velocitysensors, and TMC 1710 operates to regulate air flow 1770 based upon theone or more additional sensors. For example, air flow 1770 can belimited to a certain air flow volume, and if sensors 1742 and 1744indicate that more air flow is needed than is permitted by the air flowvolume limit, other steps to reduce the cooling demand of the serverrack, such as migrating workloads, or throttling equipment in the serverrack, can be performed.

FIG. 18 illustrates an embodiment of a server rack 1800, similar toserver rack 900, including a RMC 1810, a communication module 1820, amemory 1830, a temperature sensor 1842, a humidity sensor 1844, and avent 1860. RMC 1810 represents a service processor that is connected tocommunication module 1820, memory 1830, and sensors 1842 and 1844, andoperates to provide intelligence to server rack 1800 to gather, process,and store information related to the location and operation of theserver rack, and to permit the communication of the information to aDCMC. The information includes climate information such as thetemperature and humidity above or below the server rack 1800, climatesettings for active cooling or heating, or other information, as neededor desired. In a particular embodiment, RMC 1810 is connected to amanagement network that includes other service processors of theequipment in server rack 1800 and a management system associated withthe data center. In a particular embodiment, RMC 1810 operates inaccordance with an IPMI functional implementation. Memory 1830represents a data storage device such as a non-volatile random accessmemory (NVRAM) or another data storage device.

Communication module 1820 includes a communication port that is operableto provide communications outside of server rack 1800. In particular,the communication port can be connected to an active floor tile such asactive floor tile 1700 to provide the information from memory 1830 tothe active floor tile. In addition, the active floor tile can direct RMC1810 to update or modify the contents of the information. An example ofthe communication port includes a wired communication port, such as anRS-232 port, an Ethernet port, a USB port, a Firewire port, a CAN port,an I2C port, a SPI port, or another wired communication port, a wirelesscommunication port, such as an NFC port, WiFi port, a Bluetooth port, oranother wireless communication port, or a combination thereof.

Sensors 1842 and 1844 operate to provide RMC 1810 with informationrelated to the environment surrounding server rack 1800. For example,sensors 1842 and 1844 can be located on the top side of server rack1800, on the bottom side of the server rack, or on both the top side andthe bottom side, and RMC 1810 can provide the temperature and humidityinformation to a floor tile or to a DCMC to provide accurate, localizedfeedback as to the performance of an AC system in the data center. Inanother embodiment, sensors 1842 and 1844 can be remote from server rack1800, and the information from the sensors can be received viacommunication module 1820.

Server rack 1800 is illustrated as including a vent 1860 for permittingair flow 1870 of thermally controlled air to pass through the equipmentthe server rack. The skilled artisan will recognize that vent 1860represents one or more actual air flows through the equipment in serverrack 1800, ant that the individual air flows in the equipment may beassisted by ventilation fans in the equipment to pass the thermallycontrolled air to cool the components of the equipment. Air flow 1870passes next to sensors 1842 and 1844, and the sensors obtain ameasurement of the temperature and humidity, respectively of the airflow. RMC 1810 operates to determine if the environment surroundingserver rack 1800 is such to necessitate the supply of more or less ofair flow 1870 to the equipment in the server rack, and to communicatethe environmental information to the floor tile which can direct anactuator to position a baffle to restrict more or less of the air flow,as dictated by the environment surrounding the server rack, as describedabove. Alternatively, RMC 1810 operates communicate the environmentalinformation to a temperature control module, such as temperature controlmodule 1670 to provide preemptive/proactive cooling of the equipment inserver rack 1800. In a particular embodiment, temperature sensors 1842include a temperature sensor located at the bottom front of server rack1800 to measure the temperature of the temperature controlled airentering the environment of the server rack, and another temperaturesensor located at the top rear or the server rack to measure thetemperature of the air leaving the environment of the server rack. Inanother embodiment, humidity sensors 1844 include a humidity sensorlocated at the bottom front of server rack 1800 to measure the humidityof the temperature controlled air entering the environment of the serverrack, and another humidity sensor located at the top rear or the serverrack to measure the humidity of the air leaving the environment of theserver rack.

Returning to FIG. 16, in a particular embodiment, server racks 112-120are similar to server rack 1800, and floor tiles 132-140 are similar tofloor tile 1700. Here, one or more of RMC 1612, TMC 1632, andtemperature control module 1670 operate to control whether or not air ispermitted to flow through vent 1652. In particular the environmentsurrounding floor tile 132, such as below the floor tile and above thefloor tile, and the environment surrounding server rack 112, such as atthe bottom front of the server rack and from the top rear of the serverrack, is provided to the selected one or more of RMC 1612, TMC 1632, andtemperature control module 1670. Here the selected device determines ifthe equipment in server rack 112 is in need of more or less air flow1690, and operates an actuator similar to actuator 1762 to position abaffle similar to baffle 1764 to restrict more or less of the air flow,as dictated by the environment surrounding the server rack and floortile 132. Similarly, server racks 114-120, floor tiles 134-140, andtemperature control module 1670 operate to control whether or not air ispermitted to flow through respective vents 1654-1660.

In another embodiment, one or more of RMC 1612, TMC 1632, andtemperature control module 1670 operates to provide preemptive/proactivecooling of the equipment in server rack 112 on a per rack basis or on adata center wide basis. Here, in a first case, RMC 1612 operates todetect a change in the power usage of server rack 112. For example,server rack 112 can be similar to server rack 1500, and is operable todetect changes in the power consumption of the equipment in the serverrack. In this case, one or more of RMC 1612, TMC 1632, and temperaturecontrol module 1670 operate to control whether or not air is permittedto flow through vent 1652 to preemptively anticipate the air flow needsof server rack 112, based upon the detected change in power consumptionand to proactively provide the needed air flow for the anticipated need.For example, where the power consumption of server rack 112 is detectedto have increased, the selected device can direct the actuator toposition the baffle to permit more air flow, and where the powerconsumption of the server rack is detected to have decreased, theselected device can direct the actuator to position the baffle to permitless air flow. Similarly, server racks 114-120, floor tiles 134-140, andtemperature control module 1670 operate to control whether or not air ispermitted to flow through respective vents 1654-4660 based upon changesin the power consumption of the equipment in the server racks.

In a second case, RMC 1612 operates to recognize a routine change in thepower usage of server rack 112. For example, server rack 112 can besimilar to server rack 1500, and is not only operable to detect changesin the power consumption of the equipment in the server rack, but alsois operable to provide a power consumption analysis over time todetermine that server rack 112 has recognizable time periods ofincreased power consumption and recognizable time periods of decreasedpower consumption. In this case, one or more of RMC 1612, TMC 1632, andtemperature control module 1670 operate to control whether or not air ispermitted to flow through vent 1652 to preemptively anticipate the airflow needs of server rack 112, based upon the power consumption analysisand to proactively provide the needed air flow for the anticipated need.For example, where the power consumption of server rack 112 is analyzedto be routinely higher between 8 am and 12 pm on Monday through Friday,the selected device can direct the actuator to position the baffle topermit more air flow to the server rack, beginning at 7:55 am on Mondaythrough Friday, and where the power consumption of the server rack isanalyzed to be routinely tower between 2 am and 5 am each day of theweek, the selected device can direct the actuator to position the baffleto permit less air flow, beginning at 1:55 am on each day of the week.Similarly, server racks 114-120, floor tiles 134-140, and temperaturecontrol module 1670 operate to control whether or not air is permittedto flow through respective vents 1654-1660 based upon a powerconsumption analysis over time for the equipment in the server racks.

In a second case, temperature control module 1670 operates to recognizea routine change in the power usage of data center 100, Here, serverracks 112-120 each provide a power consumption analysis over time toDCMC 150, and temperature control module 1670 aggregates the informationto determine that data center 100 has recognizable time periods ofincreased power consumption and recognizable time periods of decreasedpower consumption. In this case, temperature control module 1670operates to control a temperature setting for the AC system topreemptively anticipate the cooling needs of data center 100 based uponthe power consumption analysis. For example, where the power consumptionof data center 100 is analyzed to be routinely higher between 8 am and12 pm on Monday through Friday, temperature control module 1670 canincrease a temperature setting for the AC system beginning at 7:50 am onMonday through Friday, and where the thermal load of the data center isanalyzed to be routinely lower between 2 am and 5 am each day of theweek, the temperature control module can decrease the temperaturesetting for the AC system beginning at 1:50 am on each day of the week.

FIG. 19 illustrates an embodiment of an active floor tile 1900, similarto active floor tile 400, including a TMC 1910, a communication module1920, a memory 1930, and a power source 1950. Power source 1950 includesa power generator 1952. TMC 1910 represents a service processor that isconnected to communication module 1920, memory 1930, and power source1950, and operates to provide intelligence to floor tile 1900 to gather,process, and store information related to the location and operation ofthe floor tile, and to permit the communication of the information. In aparticular embodiment, TMC 1910 is connected to a management networkthat includes other service processors of equipment and a server rack,and a management system associated with the data center. In a particularembodiment, TMC 1910 operates in accordance with an IPMI functionalimplementation. Memory 1930 represents a data storage device such as anon-volatile random access memory (NVRAM) or another data storagedevice.

Communication module 1920 includes a communication port that is operableto provide communications outside of floor tile 1900. In particular, thecommunication port can be connected to a server rack, to provide theinformation from memory 1930 to the server rack. In addition, the serverrack can direct TMC 1910 to update or modify the contents of theinformation. An example of the communication port includes a wiredcommunication port, such as an RS-232 port, an Ethernet port, a USBport, a Firewire port, a CAN port, an I2C port, a SPI port, or anotherwired communication port, a wireless communication port, such as an NFCport, a WiFi port, a Bluetooth port, or another wireless communicationport, or a combination thereof.

Power generator 1952 is situated in air flow 1960 of conditioned airfrom the AC system, and to generate power for floor tile 1900 from theair flow. In particular, power generator 1952 represents a wind poweredgenerator or alternator, and power source 1950 operates to receive a DCor AC voltage from the power generator and utilize the received voltageto power the components of floor tile 1900. In a particular embodiment,power source 1950 includes a battery and utilized the received voltagefrom power generator 1952 to keep the battery charged. In this way,power generator 1952 can be sized to provide an amount of power to floortile 1900 that is matched to the average power consumption of the floortile, and does not need to be sized to provide an amount of power thatis matched to the peak power consumption of the floor tile.

FIG. 20 illustrates an embodiment of an active floor tile 2000, similarto active floor tile 400, including TMC 2010, a communication module2020, a memory 2030, a weight sensor 2046, and a power source 2050. TMC2010 represents a service processor that is connected to communicationmodule 2020, memory 2030, weight sensor 2046, and power source 2050, andoperates to provide intelligence to floor tile 2000 to gather, process,and store information related to the location and operation of the floortile, and to permit the communication of the information. Theinformation includes weight information such as a detected weight of aserver rack and equipment that is located on floor tile 2000, a weightlimit for the server rack and equipment that is located on the floortile, or other information, as needed or desired. In a particularembodiment, TMC 2010 is connected to a management network that includesother service processors of the equipment and the server rack and amanagement system associated with the data center. In a particularembodiment, TMC 2010 operates in accordance with an IPMI functionalimplementation. Memory 2030 represents a data storage device such as anon-volatile random access memory (NVRAM) or another data storagedevice.

Communication module 2020 includes a communication port that is operableto provide communications outside of floor tile 2000. In particular, thecommunication port can be connected to a server rack such as server rack1800, described below, to provide the information from memory 2030 tothe server rack. In addition, the server rack can direct TMC 2010 toupdate or modify the contents of the information. An example of thecommunication port includes a wired communication port, such as anRS-232 port, an Ethernet port, a USB port, a Firewire port, a CAN port,an I2C port, a SPI port, or another wired communication port, a wirelesscommunication port, such as an NFC port, a WiFi port, a Bluetooth port,or another wireless communication port, or a combination thereof.

Weight sensor 2046 operates to provide TMC 2010 with information relatedto the weight of equipment that is located on floor tile 2000. Forexample, sensor 2046 can represent a strain gage or a mechanical scaledevice embedded in the top side of floor tile 2000, and TMC 2010 canprovide the weight information to a server rack or to a DCMC. In aparticular embodiment, TMC 2010 receives the weight information fromweight sensor 2046, compares it with a weight limit for floor tile 2000as stored in memory 2030, and provides an alert to a RMC or a DCMC whenthe detected weight exceeds the weight limit. In another embodiment, TMC2010 receives the weight information from weight sensor 2046, where theweight information shows that the weight of the equipment on floor tile2000 is either increasing, indicating that equipment has been added tothe server rack, or decreasing, indicating that the equipment has beenremoved from the server rack. Here, TMC 2010 provides an alert to theRMC or the DCMC that equipment has been added to or removed from theserver rack. In another embodiment, where one server rack is locatedatop two or more floor tiles similar to floor tile 2000, the floor tilesadd the weight information received from their respective weightsensors, and the weight limit stored in the respective memoriesrepresents a total weight limit for the two or more floor tiles.

FIG. 21 illus rates an embodiment of a server rack 2100, similar toserver rack 900, including a RMC 2110, a communication. module 2120, amemory 2130, and a weight sensor 2146. RMC 2110 represents a serviceprocessor that is connected to communication module 2120, memory 2130,and weight sensor 2146, and operates to provide intelligence to serverrack 2100 to gather, process, and store information related to thelocation and operation of the server rack, and to permit thecommunication of the information. The information includes weightinformation such as a detected weight of equipment that is installed inserver rack 2100, a weight limit for the equipment that is installed inthe server rack, or other information, as needed or desired. In aparticular embodiment, RMC 2110 is connected to a management networkthat includes other service processors of the equipment in server rack2100 and a management system associated with the data center. In aparticular embodiment, RMC 2110 operates in accordance with an IPMIfunctional implementation. Memory 2130 represents a data storage devicesuch as a non-volatile random access memory (NVRAM) or another datastorage device.

Communication module 2120 includes a communication port that is operableto provide communications outside of server rack 2100. In particular,the communication port can be connected to an active floor tile such asactive floor tile 1700 to provide the information from memory 2130 tothe active floor tile. In addition, the active floor tile can direct RMC2110 to update or modify the contents of the information. An example ofthe communication port includes a wired communication port, such as anRS-232 port, an Ethernet port, a USB port, a Firewire port, a CAN port,an I2C port, a SPI port, or another wired communication port, a wirelesscommunication port, such as an NFC port, a WiFi port, a Bluetooth port,or another wireless communication port, or a combination thereof.

Weight sensor 2146 operates to provide RMC 2110 with information relatedto the weight of equipment that is installed in server rack 2100. Forexample, sensor 2146 can represent a strain gage or a mechanical scaledevice embedded in the bottom of server rack 2100, and RMC 2110 canprovide the weight information to an active floor tile or to a DCMC. Ina particular embodiment, RMC 2110 receives the weight information fromweight sensor 2146, compares it with a weight limit for floor tile 2100as stored in memory 2130, and provides an alert to a TMC or a DCMC whenthe detected weight exceeds the weight limit. In another embodiment, RMC2110 receives the weight information from weight sensor 2146, where theweight information shows that the weight of the equipment in server rack2100 is either increasing, indicating that equipment has been added tothe server rack, or decreasing, indicating that the equipment has beenremoved from the server rack. Here, RMC 2110 provides an alert to theTMC or the DCMC that equipment has been added to or removed from theserver rack.

FIG. 22 illustrates an embodiment of a server rack 2200 including a footassembly 2210, a weight assembly 2220, a server rack structural element2230, and fasteners 2240. Foot assembly 2210 includes a foot 2212, aretaining bracket 2214, an adjusting nut 2216, and a threaded shaft2218. Weight assembly 2220 includes a sliding bracket 2222, a scaleelement 2224, and a weight sensor 2226. Structural element 2230 includesslots 2232. Foot assembly 2210 represents one of multiple similar footassemblies associated with server rack 2200. Foot assembly 2210 ismechanically affixed to server rack structural element 2230 by fasteners2240 such that when retaining bracket 2214 is elevated, server rack 2200is lifted away from a floor 2250, and when the retaining bracket islowered, the server rack is dropped closer to the floor. Foot assembly2210 is adjustable to engage foot 2212 with floor 2250 to lift serverrack 2200 away from the floor in order to provide a stable base for theoperation of the server rack, and to disengage the foot from the floorand to drop the server rack closer to the floor, permitting casters ofthe server rack (not illustrated) to be engaged with the floor such thatthe server rack can be moved from one location to another. To engagefoot 2212 with floor 2250, a rotation is applied to adjusting nut 2216which rotates threaded shaft 2218 in retaining bracket 2214 to move thefoot downward and to lift server rack 2200 off of the casters. Todisengage foot 2212 from floor 2250, an opposite rotation is applied toadjusting nut 2216 which rotates threaded shaft 2218 in retainingbracket 2214 to move the foot upward and to lower server rack 2200 ontothe casters.

Foot assembly 2210 is movably affixed to server rack structural element2230. In this regard, foot assembly 2210 is fixed to server rackstructural element 2230 in a horizontal direction, but is free to movein a vertical direction to the extent that fasteners 2240 are limited byslots 2232. As such, when foot 2212 is adjusted such that the foot isoff of floor 2250, foot assembly 2210, sliding bracket 2222 andfasteners 2240 are at a lower extreme of slots 2232. In this position,scale element 2224 is calibrated to register a minimum weight. Forexample, when positioned at the lower extreme of slots 2232, scaleelement 2224 can be calibrated to read a weight of server rack 2200 onfoot 2212 of “zero” (e.g., pounds, kilograms, or other, as needed ordesired), or the scale element can be calibrated to read a weight of theserver rack as predetermined at a factory. Further, when foot 2212 isadjusted such that the foot is fully engaged with the floor (e.g., whenthe foot is supporting one quarter of the weight of server rack 2200 andthe equipment installed therein), foot assembly 2210, sliding bracket2222 and fasteners 2240 are at a higher extreme of slots 2232. In thisposition, scale element 2224 is calibrated to register a non-minimumweight. For example, when positioned at the higher extreme of slots2232, scale element 2224 can be calibrated to read a weight of serverrack 2200 and the installed equipment on foot 2212, or the scale elementcan be calibrated to read a weight of just the installed equipment. Theskilled artisan will recognize that the above discussion was in terms ofa single foot assembly 2100, but that the actual measurements will be ofthat portion of the weight of server rack 2100 and the installedequipment that is supported by the foot assembly, and that otherportions of the weight of the server rack and the installed equipmentwill be measured by the other foot assemblies, giving a total weight ofthe server rack and the installed equipment. Moreover, the skilledartisan will recognize that the level of the higher extreme of slots2232 to which foot assembly 2210, sliding bracket 2222 and fasteners2240 are positioned will depend on the weight of server rack 2200 andthe equipment installed therein, and that a greater or lesser weightwill result in the foot assembly, the sliding bracket, and the fastenersbeing located at a different, higher or lower, respectively, position.

In a particular embodiment, weight sensor 2226 operates receive anindication of the weight detected by scale element 2224, and to providea RMC associated with server rack 2200 with information related to theweight of equipment that is installed in the server rack. For example,the RMC can provide the weight information to an active floor tile or toa DCMC. In a particular embodiment, the RMC receives the weightinformation from weight sensor 2226, compares it with a weight limit forthe floor tile, and provides an alert to a TMC or a DCMC when thedetected weight exceeds the weight limit. In another embodiment, the RMCreceives the weight information from weight sensor 2226, where theweight information shows that the weight of the equipment installed inserver rack 2200 is either increasing, indicating that equipment hasbeen added to the server rack, or decreasing, indicating that theequipment has been removed from the server rack. Here, the RMC providesan alert to the TMC or the DCMC that equipment has been added to orremoved from server rack 2200.

In another embodiment, one or more of scale element 2224 and weightsensor 2226 operate to provide an indication as to whether or not foot2212 is engaged with floor 2250. In a first case, scale element 2224 isconfigured to provide a visible indication of the position of foot 2212,such as a scale read out that shows a red indication when the foot isengaged and a green indication when the foot is not engaged based uponthe amount of weight reported by the scale element. In a second case,weight sensor 2226 is configured to light a red indicator, such as a redLED indicator, when foot 2212 is engaged and a green indicator, such asa green LED indicator, when the foot is not engaged, based upon theweight indication received from scale element 2224. In an alternative,weight sensor 2226 can include a micro-switch that is engaged by foot2212 when the foot is disengaged from floor 2250, such that the actionof the micro-switch provides for the red and green indications. In aparticular embodiment, a RMC can receive an indication of the positionof foot 2212, and can report that indication via an indicator or to aDCMC.

FIG. 23 illustrates an embodiment of a server rack 2300 including footassemblies 2310, 2320, 2330, and 2340, and a leveling module 2350. Footassembly 2310 includes a foot 2312, a retaining bracket 2314, anadjusting servo 2316, and a threaded shaft 2318. Each of foot assemblies2320, 2330, and 2340 each include respective feet, retaining brackets,adjusting servos, and threaded shafts. Foot assemblies 2310, 2320, 2330,and 2340 are each mechanically affixed to a server rack structuralelement by fasteners such that when retaining bracket 2314 is elevated,server rack 2300 is lifted away from a floor 2360, and when theretaining bracket is lowered, the server rack is dropped closer to thefloor. Foot assembly 2310 is adjustable to engage foot 2312 with floor2350 to lift server rack 2300 away from the floor in order to provide astable base for the operation of the server rack, and to disengage thefoot from the floor and to drop the server rack closer to the floor,permitting casters of the server rack (not illustrated) to be engagedwith the floor such that the server rack can be moved from one locationto another. To engage foot 2312 with floor 2350, a rotation is appliedto adjusting servo 2316 which rotates threaded shaft 2318 in retainingbracket 2314 to move the foot downward and to lift server rack 2300 offof the casters. To disengage foot 2312 from floor 2350, an oppositerotation is applied to adjusting servo 2316 which rotates threaded shaft2318 in retaining bracket 2314 to move the food upward and to lowerserver rack 2300 onto the casters. Foot assemblies 2320, 2330, and 2340operate similarly to foot assembly 2310.

Leveling module 2350 is connected to adjusting servo 2316 and to theadjusting servos of foot assemblies 2320, 2330, and 2340. In aparticular embodiment, leveling module 2350 operates to detect whenserver rack 2300 is level, that is, oriented in a vertical relationshipwith floor 2360. If server rack 2300 is not level, then leveling module2350 directs one or more of adjusting servo 2316 and the adjustingservos on foot assemblies 2320, 2330, and 2340 to apply a rotation tothe associated threaded shaft in order to bring the server rack into alevel orientation. In an embodiment, foot assemblies 2310, 2320, 2330,and 2340 include a weight sensor similar to weight sensor 2226, and thedetermination that server rack 2300 is in a level orientation can bemade in conjunction with the weight distribution on the foot assemblies.An example of leveling module 2350 includes a gyroscopic sensor, adistance sensor, and level indicator, a camera, or other levelingsensor, as needed or desired. In another embodiment, a RMC receives theinformation from leveling module 2350 and directs the activities of theservos.

FIGS. 24 and 25 illustrate an embodiment of a server rack 2400 includinga RMC 2410 with a balance interlock module 2420. Server rack 2400 issimilar to server rack 900, and thus RMC 2410 is connected to acommunication module, a memory, and one or more sensors (notillustrated) of server rack 2400. Balance interlock module 2420 isconnected to an interlock 2422 associated with a rack unit an interlock2424 associated with a rack unit 2U, an interlock 2426 associated with arack unit 3U, an interlock 2428 associated with a rack unit 4U, aninterlock 2430 associated with a rack unit 5U, and an interlock 2432associated with a rack unit 6U. Balance interlock module 2420 operatesto control interlocks 2422-2432 to operate either in an open position orin an interlocked position. In the open position interlocks 2422-2432operate to permit the installation and removal of equipment from theassociated rack units. In the interlocked position interlocks 2422-2432operate to prevent the removal of equipment from the associated rackunits. In a particular embodiment, balance interlock module 2420operates to control interlocks 2422-2432 to prevent the removal ofequipment from the associated rack units as a security measure. Here,once a piece of equipment is installed in server rack 2400, theassociated interlocks 2422-2432 are set to the interlocked position, andthe interlocks are not set to the open position without an override toopen the interlocks.

In FIG. 24, the rack space of server rack. 2400 is populated with five1-U servers 2440, 2445, 2450, 2455, and 2460. Server 2440 is installedin rack space 1U, server 2445 is installed in rack space 2U, server 2450is installed in rack space 3U, server 2455 is installed in rack space5U, and server 2460 is installed in rack space 6U. Balance interlockmodule 2420 operates to determine the weight of servers 2440, 2445,2450, 2455, and 2460. In a particular embodiment, the weight of servers2440, 2445, 2450, 2455, and 2460 is determined based upon informationreceived by RMC 2410 from the servers, indicating each server's weight.In another embodiment, the weight of servers 2440, 2445, 2450, 2455, and2460 is determined based upon an estimated or average weight for theservers. For example, balance interlock module 22420 can assume that a1-U piece of equipment weighs 40 pounds, that a 241 piece of equipmentweighs 80 pounds, and so on. Based upon the weight of servers 2440,2445, 2450, 2455, and 2460, and the positions of the servers withinserver rack 2400, balance interlock module 2420 determines a center ofgravity 2475 for the equipment installed in the server rack. Moreover,balance interlock module 2420 operates to determine if center of gravity2475 is above or below a centerline 2470 of server rack 2400. Whencenter of gravity 2475 is below centerline 2470, as illustrated here, anoverride permits balance interlock module 2420 to open interlocks2422-2432. FIG. 25 illustrates a case where servers 2440, 2445, and 2450have been removed from server rack 2400. Here, balance interlock module2420 operates to recalculate anew center of gravity 2477 and todetermine that the new center of gravity is above centerline 2470, andthe balance interlock module operates to re-set interlocks 2430 and 2432to the interlocked position to prevent the removal of servers 2455 and2460. In this way, when server rack 2400 is top heavy, a technician isprevented from attempting to remove equipment from the server rackbecause of the danger of toppling the server rack when the equipment isremoved. For example, when a server rack is top heavy, the removal of alarge (i.e. 2-U, 3-U, or larger) piece of equipment may shift the centerof gravity beyond the confines of the server rack and the server rackcan fall over onto the technician. In a particular embodiment, serverrack 2400 includes a handle at the back of the server rack, beyond thereach of a single technician, that includes an override switch that canbe engaged to permit a technician to remove apiece of equipment fromatop heavy server rack. In a particular embodiment, when RMC 2410determines that center of gravity 2477 is above centerline 2470, the RMCoperates to prevent foot assemblies of server rack 2400, similar to footassemblies 2310, 2320, 2330, and 2340, from disengaging with the floor,thereby preventing the server rack from being moved when the server rackhas a high center of gravity. Further, RMC 2410 can include an overridefeature to permit the foot assemblies to disengage with the floor.

FIG. 26 illustrates a server rack 2600 including a RMC 2610, a paneldetection module 2620, and a panel ground detection module 2630. RMC2610 is connected to panel detection module 2620, and to panel grounddetection module 2630. Panel detection module 2620 operates to determineif a side panel 2640 is installed on server rack 2600 and to provide anindication to RMC 2610 as to the presence or absence of the panel. Panelground detection module 2630 operates to provide an indication as towhether or not panel 2640 is properly grounded and to provide anindication to RMC 2610 as to whether or not the panel is properlygrounded. The skilled artisan will recognize that panel detection module2620 and panel ground detection module 2630 can be implemented as asingle module operable to detect the presence of a panel and the groundstatus of the panel. Further, while described with respect to just oneside of server rack 2600, the skilled artisan will recognize that asecond panel detection module and a second panel ground detection modulecan be implemented on a second side of the server rack of for a door ofthe server rack.

FIG. 27 illustrates data center 100 of FIG. 1, where DCMC 150 includes adata center management appliance 2710 that operates to integrate themanagement and control of the data center into a unified interface. In aparticular embodiment, data center management appliance 2710 operates toaggregate and manage the information of the TMCs, RMCs, BMCs,environmental controls, and other elements of data center 100. As such,data center management appliance 2710 integrates the management andcontrol functions of DCMC 150 into a graphical user interface (GUI) thatpermits a data center administrator to access the features of datacenter 100 as described herein. For example, data center managementappliance 2710 can read, write, update, or modify information 432 ofactive floor tile 400 and information 932 of server rack 900, can accessaggregator 1140 of server rack 1100 to obtain KVM access to theequipment installed in the server tack, to manage the EMS, and to managethe serial aggregator, can map physical locations of the equipmentinstalled in server rack 1100, can update or modify the information inreal time clock 1340 of server rack 1300, can map port of the equipmentin server rack 1400, set up the vLANs for the equipment, and manage vLANsetup module 1440, can manage power mapping module 1540 and map thepower connections of server rack 1500, can receive temperature andhumidity information and adjust air flow in floor tile 1700, can receivetemperature and humidity information from server rack 1800, can receiveweight information and provide weight limits to floor tile 2000, canreceive weight information and provide weight limits to server rack2100, can receive weight information from weight sensor 2226, canreceive rack leveling information from rack leveling module 2350 ofserver rack 2300, can receive center of gravity information from balanceinterlock module 2420 of server rack 2400, and can receive paneldetection and grounding information from RMC 2610 of server rack 2600.

In a particular embodiment, data center management appliance 2710represents a function of a data center management system that isaccessible to an administrator, and the administrator interfaces withthe data center management appliance via the data center managementsystem. In another embodiment, data center management appliance 2710provides a function that is portable to a mobile device, such as a smarttelephone or a tablet device. In either case, an administrator can bepresented with a graphical representation of the entire data center 100,and can select a portion of the data center to focus on. Theadministrator can further select a particular server rack or activefloor tile to access the features presented by the server rack and theactive floor tile. The administrator can also select a particular serveror piece of equipment in the server rack and gain access to themanagement functions of the server or piece or equipment, such as via aBMC. The administrator can even access an operating system environmentof the server or piece of equipment, such as via an aggregator similarto aggregator 1140.

In another embodiment, DCMC 150 includes a preset list of tasks toexecute when a new server or server rack is installed into data center100. Here, a BMC of a new server, or a RMC of a new server rack willprovide information related to the server or server tack to DCMC 150.Based upon predetermined information, DCMC 150 operates to providepreset server names, prefixes, IP addresses, BMC names, and the like tothe server or server rack, thereby automating the setup and install ofequipment in data center 100. The preset list also includes other serverconfiguration information, such as OS installation instructions,application software installation instructions, vLAN mappings, and thelike, as needed or desired.

In another embodiment, data center management appliance 2710 operates toprovide a repair guide for an administrator of data center 100. As such,data center management appliance 2710 identifies a piece of equipment2710 that is in need of service, and provides a visual representation ofthe location of the equipment. The repair guide further providesinstructions for the specific service. For example, the repair guide caninclude instructions for replacing a field replaceable unit (FRU) suchas a disk drive, a power module, or the like. In a particularembodiment, when a service need is identified, data center managementappliance 2710 automatically issues a service ticket and provides for arequest dispatch for a replacement part if a failing part of theequipment is identified.

FIG. 28 illustrates a method for programming a passive floor tilebeginning at block 2802 where a plan for a data center is createdincluding a grid of (M,N) passive floor tiles. For example, floor 200can include passive floor tiles 202-218 in a grid of (3,3) floor tiles.An X-counter is set to 0 (zero) and a Y-counter is set to 0 (zero) inblock 2804. The X-counter is incremented by 1 (one) in block 2806, andthe Y-counter is incremented by 1 (one) in block 2808. A RFID device isprogrammed with information associated with the floor tile located atthe grid location designated by the X-counter and the Y-counter in block2810. For example, when the X- and Y-counters are both equal to 1 (one),RFID tag 203 can be programmed to store information related to thelocation of the associated floor tile 202, including the grid location,a weight limit for server racks and equipment located on. the floortile, a rang of IP addresses for the equipment, a client name associatedwith the equipment, a system name for the equipment, or otherinformation, as needed or desired.

A decision is made as to whether or not the Y-counter is equal to N indecision block 2812. If not, the “NO” branch of decision block 2812 istaken and the method returns to block 2808 where the Y-counter isincremented by 1 (one) and the next RFID device is programmed in block2810. If the Y-counter is equal to N, the “YES” branch of decision block2812 is taken and the Y-counter is reset to 0 (zero) in block 2814. Adecision is made as to whether or not the X-counter is equal to M indecision block 2816. If not, the “NO” branch of decision block 2816 istaken and the method returns to block 2806 where the X-counter isincremented by 1 (one) and the next row of RFID devices is programmed asdescribed above. If the X-counter is equal to the “YES” branch ofdecision block 2816 is taken, indicating that all of the RFID deviceshave been programmed, and the method ends in block 2818.

FIG. 29 illustrates a method for communicating information from apassive floor tile to a server rack beginning at block 2902 where aserver rack is rolled onto a floor tile. For example, server rack 310can be rolled onto floor tile 202. A decision is made as to whether ornot the floor tile includes an RFID device in decision block 2904. Forexample, RFID tag reader 312 in server rack 310 can detect the presenceor absence of an RFID device in the floor tile. If the floor tile doesnot include an RFID device, the “NO” branch of decision block 2904 istaken and the method ends at block 2908. If the floor tile includes anRFID device, the “YES” branch of decision block 2904 is taken, theserver rack reads the information from the passive floor tile in block2906, and the method ends at block 2908.

FIG. 30 illustrates a method for pre-programming an active floor tilebeginning at block 3002 where a plan for a data center is createdincluding a grid of (M,N) active floor tiles. For example, floor 500 caninclude active floor tiles 502-518 in a grid of (3,3) floor tiles. AnX-counter is set to 0 (zero) and a Y-counter is set to 0 (zero) in block3004. The X-counter is incremented by 1 (one) in block 3006, and theY-counter is incremented by 1 (one) in block 3008. A memory of an activefloor tile is stored with information associated with the floor tilelocated at the grid location designated by the X-counter and theY-counter in block 3010. For example, when the X- and Y-counters areboth equal to 1 (one), active floor tile 502 can be programmed to storeinformation related to the location of the floor tile, including thegrid location, a weight limit for server racks and equipment located onthe floor tile, a range of IP addresses for the equipment, a client nameassociated with the equipment, a system name for the equipment, or otherinformation, as needed or desired.

A decision is made as to whether or not the Y-counter is equal to N indecision block 3012. If not, the “NO” branch of decision block 3012 istaken and the method returns to block 3008 where the Y-counter isincremented by 1 (one) and the information for the next active floorpanes is stored in the memory device in block 3010. If the Y-counter isequal to N, the “YES” branch of decision block 3012 is taken and theY-counter is reset to 0 (zero) in block 3014. A decision is made as towhether or not the X-counter is equal to M in decision block 3016. Ifnot, the “NO” branch of decision block 3016 is taken and the methodreturns to block 3006 where the X-counter is incremented by 1 (one) andthe next row of RFID devices is programmed as described above. If theX-counter is equal to M, the “YES” branch of decision block 3016 istaken, indicating that all of the RFID devices have been programmed, andthe method ends in block 3018.

FIG. 31 illustrates a method for networking active floor tiles beginningat block 3102 where a plan for a data center is created including a gridof (M,N) active floor tiles. For example, floor 600 can include activefloor tiles 602-618 in a grid of (3,3) floor tiles. The active floortiles are installed in the data center floor, and the floor tiles areinterconnected in block 3104. For example, the active floor tiles caneach be connected to a DCMC, as depicted in FIGS. 5 and 6, the activefloor tiles can be connected to each other with a single floor tileconnected to the DCMC, as depicted in FIGS. 7 and 8, or the floor tilescan be otherwise interconnected, as needed or desired. The active floortiles discover their positions on the grid of the floor in block 3106,and a memory of the active floor tiles is stored with informationassociated with each floor tile based upon their location on the grid.For example, active floor tile 502 can be programmed to storeinformation related to the location of the floor tile, including thegrid location, a weight limit for server racks and equipment located onthe floor tile, a range of IP addresses for the equipment, a client nameassociated with the equipment, a system name for the equipment, or otherinformation, as needed or desired.

FIG. 32 illustrates a method for communicating information between anactive floor tile and a server rack beginning at block 3202 where aserver rack is connected to an active floor tile. For example, activefloor tile 1010 can be connected to server rack 1020. A determination ismade as to whether or not the active floor tile is programmed indecision block 3204. If so, the “YES” branch of decision block 3204 istaken and the server rack receives information related to the locationof the server rack from the active floor tile in block 3206, and themethod ends in block 3208. For example, memory 1016 of active floor tile1010 can include tile information 1017 related to the location of thefloor tile, including the grid location, a weight limit for server racksand equipment located on the floor tile, a range of IP addresses for theequipment, a client name associated with the equipment, a system namefor the equipment, or other information, as needed or desired. If theactive floor tile is not programmed, the “NO” branch of decision block3204 is taken and a DCMC is queried by a RMC for information to provideto the active floor tile in block 3210. The RMC communicates theinformation to the active floor tile and the information is stored inthe memory of the active floor tile in block 3212 and the method ends inblock 3208.

FIG. 33 illustrates a method for finding a physical location ofequipment in a server rack beginning at block 3302 where a server rackis provided with a rack space. For example server rack 1100 can includea rack space 1110. A service port is associated with a rack unit of therack space in block 3304. For example, service port 1142 can beassociated with rack unit 1112, such that aggregator 1140 candistinguish the service port because each service port is connected to aunique port of the aggregator. A server is installed into the rack unitin block 3306. For example, server 1190 can be installed into rack unit1122. A service port of the server is connected to the service port ofthe rack unit in block 3308. For example, service port 1192 of server1190 can be plugged into service port 1152 of rack unit 1122 viaconnector cable 1194. The physical location of the server is determinedbased upon the fact that the service port of the server is connected tothe service port of the rack unit in block 3310. For example, becauseservice port 1192 is plugged into service port 1152, the physicallocation of the server is determined to be in rack unit 1122. A decisionis made as to whether or not the rack unit is the last rack unit of theserver rack in decision block 3312. If so, the “YES” branch of decisionblock 3312 is taken and the method ends in block 3316. If the rack unitis not the last rack unit of the server rack, the “NO” branch ofdecision block 3312 is taken, the next rack unit is considered in block3314, and the method proceeds to block 3304 where a next service port isassociated with the next rack unit.

FIG. 34 illustrates a method for providing a real time clock toequipment in a server rack beginning at block 3402 where a server isconnected to a rack unit service port. For example, service port 1362 ofserver 1360 can be connected to service port 1342. The server receivesreal time clock information from the service port of the rack unit inblock 3404, and the method ends in block 3406. In a particularembodiment, the server does not include its own separate real time clockfunction, thereby saving on the cost of the components to provide thereal time clock function, and also saving space on the motherboard ofthe server.

FIG. 35 illustrates a method for mapping network ports and vLANs in aserver rack beginning at block 3502 where a server rack is provided witha rack space. For example server rack 1400 can include a rack space. Aservice port is associated with a rack unit of the rack space in block3504. For example, service port 1442 can be associated with a rack unit,such that vLAN setup module 1440 can distinguish the service portbecause each service port is connected to a unique port of the vLANsetup module. A server is installed into the rack unit in block 3506.For example, server 1460 can be installed into the rack unit. A serviceport of the server is connected to the service port of the rack unit inblock 3508. For example, service port 1462 of server 1460 can be pluggedinto service port 1442 of the rack unit. A host port of the server isconnected to a server rack switch in block 3510. For example, host port1466 of server 1460 can be connected to host port 1452 of rack switch1450. A service port of the server rack switch is connected to a serviceport of a RMC in block 3512. For example, service port 1459 of serverrack switch 1450 can be connected to service port 1432 of RMC 1430.

The host ports are mapped to the switch and the vLAN associations forthe switch are determined based upon the service port connections andthe host port connections with the server in block 3514, and the servervLANs are mapped in the server rack switch in block 3516. A decision ismade as to whether or not the rack unit is the last rack unit of theserver rack in decision block 3518. If so, the “YES” branch of decisionblock 3518 is taken and the method ends in block 3522. If the rack unitis not the last rack unit of the server rack, the “NO” branch ofdecision block 3518 is taken, the next rack unit is considered in block3520, and the method proceeds to block 3504 where a next service port isassociated with the next rack unit.

FIG. 36 illustrates a method for mapping power connections in a serverrack beginning at block 3602 where a server rack is provided with a rackspace. For example server rack 1500 can include a rack space. A powerreceptacle is associated with a rack unit of the rack space in block3604. For example, power receptacle 1542 can be associated with rackunit of server rack 1500, such that power mapping module 1440 candistinguish the power receptacle because each power receptacle providesan individual indication to the power mapping module. A server isinstalled into the rack unit in block 3606. For example, server 1590 canbe installed into the rack unit. A power receptacle of the server isconnected to the power receptacle of the rack unit in block 3608. Forexample, power receptacle 1592 of server 1590 can be plugged into powerreceptacle 1552 of the rack unit. The physical location of the server isdetermined based upon the fact that the power receptacle of the serveris connected to the power receptacle of the rack unit in block 3610. Forexample, because power receptacle 1592 is plugged into power receptacle1552, the physical location of the server is determined to be in theparticular rack unit. A decision is made as to whether or not the rackunit is the last rack unit of the server rack in decision block 3612. Ifso, the “YES” branch of decision block 3612 is taken and the method endsin block 3616. If the rack unit is not the last rack unit of the serverrack, the “NO” branch of decision block 3612 is taken, the next rackunit is considered in block 3614, and the method proceeds to block 3604where a next service port is associated with the next rack unit.

FIG. 52 illustrates a method of determining the physical location of aserver in a server rack, such as is described in block 3610 of FIG. 36.The method includes steps 5210 performed in the server and steps 5230performed in the server rack. In a particular embodiment, steps 5210 areperformed by one or more of a BMC associated with the server, a PLCmodule in the power supply of the server, or by another device of theserver, and steps 5230 are performed by one or more of a RMC of theserver rack, a PDU of the server rack, or by another device of theserver rack. The method starts in the server at block 5212, and theserver asserts an interrupt request (IRQ) via a management network tothe server rack in block 5214. The server awaits an acknowledgement(ACK) of the IRQ from the server rack in decision block 5216. When theserver receives the ACK from the server rack, the “YES” branch ofdecision block 5216 is taken and the server awaits a unique U-spacelocation identification from the server rack in decision block 5218.When the server receives the unique U-space location identification fromthe server rack, the “YES” branch of decision block 5218 is taken, theserver sends an ACK to the server rack via a PLC over the AC port inblock 5220, and the method ends in block 5222.

In the server rack, the IRQ from block 5214 is received and is pushedonto an IRQ stack in block 5232. A decision is made as to whether or notthe stack is empty in decision block 5234. If so, the “YES” branch ofdecision block 5234 is taken and the method ends in block 5236. However,if the stack is not empty, the “NO” branch of decision block 5234 istaken and the server rack provides an ACK to the server, to decisionblock 5216, via the management network in block 5238. The IRQ from theserver is processed in the server rack in block 5240 and a uniqueU-space location identification is broadcast on each AC Port, therebyproviding the unique U-space location identification to the server, todecision block 5218, in block 5242. The server rack awaits an ACK of theunique U-space location identification from the server, from block 5220,in decision block 5244. When the server rack receives the ACK from theserver, the “YES” branch of decision block 5244 is taken, the serverlocation is recorded by the server rack in block 5246, the IRP is poppedoff of the stack in block 5248, and the method returns to decision block5234 to process a next IRQ until all IRQs are processed.

FIG. 37 illustrates a method for managing the running average power in aserver rack beginning at block 3702 where a RMC receives power usagelevels for the power receptacles of the server rack. For example, RMC1530 can receive the power usage level for power receptacle 1552. Adecision is made as to whether or not the power usage level is greaterthan a power usage limit in decision block 3704. If not, the “NO” branchof decision block 3704 is taken and the method returns to block 3702where the RMC receives power usage levels for the power receptacles ofthe server rack. If the power usage level is greater than a power usagelimit, the “YES” branch of decision block 3704 is taken, the RMCthrottles the server in block 3706, and the method returns to block 3702where the RMC receives power usage levels for the power receptacles ofthe server rack.

FIG. 37 also illustrates a method for managing the running average powerin a data center beginning at block 3712 where a DCMC receives powerusage levels for a server rack. A decision is made as to whether or notthe power usage level is greater than a power usage limit in decisionblock 3714. If not, the “NO” branch of decision block 3714 is taken andthe method returns to block 3702 where the DCMC receives power usagelevels for the server rack. If the power usage level is greater than apower usage limit, the “YES” branch of decision block 3714 is taken, theDCMC migrates one or more virtual machines from the server rack in block3716, and the method returns to block 3712 where the DCMC receives powerusage levels for the server rack.

FIG. 38 illustrates a method for operating servers in various standbymodes beginning at block 3802 where a first high utilization limit(UL_(HIGH1)), a second high utilization limit (UL_(HIGH2)), a first lowutilization limit (UL_(LOW1)), and a second low utilization limit(UL_(LOW2)) are set. In a particular embodiment, the limits are set fora particular server rack in a data center. In another embodiment, thelimits are set for the whole data center. A number of servers that areon (S_(ON)), a number of servers that are in standby (S_(SB)), and anumber of servers that are off (S_(OFF)), are determined in block 3804.A server usage level is determined in block 3806. In a particularembodiment, the server usage level is determined for the server rack. Inanother embodiment, the server usage level is determined for the wholedata center.

A decision is made as to whether or not the server usage level isgreater than UL_(HIGH1) in decision block 3808. If not, the “NO” branchof decision block 3808 is taken and a decision is made as to whether ornot the server usage level is less than UL_(LOW1) in decision block3810. If not, the “NO” branch of decision block 3810 is taken and themethod returns to block 3806 where the server usage level isre-determined. In this sequence of events, the server usage level isdetermined to be within a nominal range and no changes are made toS_(ON), S_(SB), or S_(OFF).

Returning to decision block 3808, if the server usage level is greaterthan UL_(HIGH1), the “YES” branch is taken, S_(SB) is increased by 1(one) server, that is, the number of severs in the standby state isincreased by 1 (one), in block 3812, and a decision is made as towhether or not the server usage level is also greater than UL_(HIGH2) indecision block 3814. If not, the “NO” branch of decision block 3814 istaken and the method returns to block 3806 where the server usage levelis re-determined. If the server usage level is also greater thanUL_(HIGH2), the “YES” branch of decision block 3814 is taken, S_(ON) isincreased by 1 (one) server, that is, the number of severs in the in thepower-on state is increased by 1 (one) in block 3816, and the methodreturns to block 3806 where the server usage level is re-determined.

Returning to decision block 3810, if the server usage level is less thanUL_(LOW1), the “YES” branch is taken, S_(SB) is decreased by 1 (one)server, that is, the number of severs in the standby state is decreasedby 1 (one), in block 3818, and a decision is made as to whether or notthe server usage level is also less than UL_(LOW2) in decision block3820. If not, the “NO” branch of decision block 3820 is taken and themethod returns to block 3806 where the server usage level isre-determined. If the server usage level is also less than UL_(LOW2),the “YES” branch of decision block 3820 is taken, S_(OFF) is increasedby 1 (one) server, that is, the number of severs in the in the power-offstate is increased by 1 (one) in block 3822, and the method returns toblock 3806 where the server usage level is re-determined.

FIG. 39 illustrates a method for operating a floor tile with an activevent beginning at block 3902. An air flow needed for a server rack isdetermined in block 3904. For example, one or more of an active floortile such as active floor tile 1700 and a server rack 1800 can measurethe temperature and the humidity of the thermally controlled air in thevicinity of the server rack to determine if more or less of thethermally controlled air is needed by the serve rack. A decision is madeas to whether or not more air flow is needed by the server rack indecision block 3906. If not, the “NO” branch of decision block 3906 istaken and a decision is made as to whether or not less air flow isneeded b the server rack in decision block 3908. If not, the “NO” branchof decision block 3908 is taken and the method returns to block 3904where the air flow needed for a server rack is determined. In thissequence of events, the air flow provided to the server rack issufficient to the cooling needs of the server rack.

Returning to decision block 3906, if more air flow is needed by theserver rack, then the “YES” branch is taken, one or more of the DCMC,the RMC, and the TMC operate to direct the active floor the to provideadditional air flow to the server rack in block 3910, and method returnsto block 3904 where the air flow needed for a server rack is determined.For example, TMC 1710 can operate to direct actuator 1762 to positionbaffle 1764 to restrict less of air flow 1770 to provide additionalthermally controlled air to the server rack. Returning to decision block3908, if less air flow is needed by the server rack, then the “YES”branch is taken, one or more of the DCMC, the RMC, and the TMC operateto direct the active floor tile to provide less air flow to the serverrack in block 3912, and method returns to block 3904 where the air flowneeded for a server rack is determined. For example, TMC 1710 canoperate to direct actuator 1762 to position baffle 1764 to restrict moreof air flow 1770 to provide less thermally controlled air to the serverrack.

FIG. 40 illustrates a method for closed loop thermal control of a serverrack and a data center beginning at block 4002. An air flow needed for adata center is determined in block. 4004. For example, one or more of anactive floor tile such as active floor tile 1700 and a server rack 1800can measure the temperature and the humidity of the thermally controlledair in the vicinity of the server rack to determine if more or less ofthe thermally controlled air is needed by the serve rack, and a DCMC canmeasure the temperature and humidity of the thermally controlled airleaving and entering the data center AC system. A decision is made as towhether or not more air flow is needed in the data center in decisionblock 4006. If not, the “NO” branch of decision block 4006 is taken anda decision is made as to whether or not less air flow is needed bin thedata center in decision block 4008. If not, the “NO” branch of decisionblock 4008 is taken and the method returns to block 4004 where the airflow needed for the data center is determined. In this sequence ofevents, the air flow provided to the data center is sufficient to thecooling needs of the server racks in the data center. Returning todecision block 4006, if more air flow is needed by the data center, thenthe “YES” branch is taken, the DCMC operates to direct the AC system toprovide additional air flow to the data center in block 4010, and methodreturns to block 4004 where the air flow needed for the data center isdetermined. Returning to decision block 4008, if less air flow is neededby the data center, then the “YES” branch is taken, the DCMC operates todirect the AC system to provide less air flow to the data center inblock 4012, and method returns to block 4004 where the air flow neededfor a server rack is determined.

FIG. 41 illustrates a method for (preemptive/proactive cooling of aserver rack beginning at block 4102. A change in the power usage of aserver or a server rack is detected in block 4104. For example, RMC 1810can detect the power usage of one or more servers in server rack 1800,and can detect when the level of the power usage changes for one or moreserver. A decision is made as to whether or not the power usage in theserver rack has increased in decision block 4106. If not, the “NO”branch of decision block 4106 is taken and a decision is made as towhether or not the power usage in the server rack has decreased indecision block 4108. If not, the “NO” branch of decision block 4108 istaken and the method returns to block 4104 where a change in the powerusage of the server or the server rack is detected. In this sequence ofevents, the power usage of the servers and the server rack is unchanged.

Returning to decision block 4106, if the power usage in the server rackhas increased, then the “YES” branch is taken, one or more of the DCMC,the RMC, and the TMC operate to direct additional air flow to the serverrack in block 4110, and method returns to block 4104 where a change inthe power usage of the server or the server rack is detected. Forexample, RMC 1810 can direct TMC 1710 to operate actuator 1762 toposition baffle 1764 to restrict less of air flow 1770 to provideadditional thermally controlled air to the server rack. Returning todecision block 4108, if the power usage in the server rack hasdecreased, then the “YES” branch is taken, one or more of the DCMC, theRMC, and the TMC operate to direct less air flow to the server rack inblock 4112, and method returns to block 4104 where a change in the powerusage of the server or the server rack is detected. For example, RMC1810 can direct TMC 1710 to operate actuator 1762 to position baffle1764 to restrict more of air flow 1770 to provide less thermallycontrolled air to the server rack.

FIG. 41 also illustrates a method for preemptive/proactive cooling of adata center beginning at block 4122. One or more of a RMC and a DCMCdetects a periodic change in the power usage of a data center in block4124. For example, RMC 1810 can detect when the power usage of one ormore servers in server rack 1800 varies with time. A decision is made asto whether or not the power usage in the data center periodicallyincreases in decision block 4126. If not, the “NO” branch of decisionblock 4126 is taken and a decision is made as to whether or not thepower usage in the data center periodically decreases in decision block4128. If not, the “NO” branch of decision block 4128 is taken and themethod returns to block 4124 where one or more of a RMC and a DCMCdetects a periodic change in the power usage of a data center. In thissequence of events, the power usage has not periodically changed.

Returning to decision block 4126, if the power usage in the data centerperiodically increases, then the “YES” branch is taken, the DCMCoperates to direct the AC system to reduce a temperature setting for thethermally controlled air in the data center in block 4130, and methodreturns to block 4124 where one or more of a RMC and a DCMC detects aperiodic change in the power usage of a data center. For example, DCMC150 can direct the AC system to reduce the temperature setting in datacenter 100. Returning to decision block 4128, if the power usage in thedata center periodically decreases, then the “YES” branch is taken, theDCMC operates to direct the AC system to increase the temperaturesetting for the thermally controlled air in the data center in block4132, and method returns to block 4124 where one or more of a RMC and aDCMC detects a periodic change in the power usage of a data center. Forexample, DCMC 150 can direct the AC system to increase the temperaturesetting in data center 100.

FIG. 42 illustrates a method for active power generation for an activefloor tile beginning at block 4202 where an active floor tile is placedonto a data center floor. For example, active floor tile 1900 can beplaced into a data center floor. An air flow is provided in a sub-floorarea of the data center floor in block 4204. For example, air flow 1960can be provided in the sub-floor area below active floor tile 1900.Power is generated for the active floor tile from the airflow in thesub-floor in block 4206, and the method ends in block 4208. For example,active floor tile 1900 can receive operating power from power generator1952.

FIG. 43 illustrates a method for reporting the weight of a server rackbeginning at block 4302 where one or more of an active floor tile and aserver rack are programmed with weight limit information for the floortile in block 4302. For example, one or more of memory 2030 of activefloor tile 2000, and memory 2130 of active floor tile 2100 can beprogrammed with weight limit information for the floor tile. The serverrack is installed on the active floor tile in block 4304. For example,server rack 2100 can be installed on active floor tile 2000. One or moreof the active floor tile and the server rack measures the weight of theserver rack in block 4308. For example, one or more of weight sensor2046 and weight sensor 2146 can measure the weight of server rack 2100.

A decision is made as to whether or not the measured weight has changedin block 4310. If not, the “NO” branch of decision block 4310 is takenand a decision is made as to whether or not the measured weight isgreater than the weight limit information in decision block 4312. Ifnot, the “NO” branch of decision block 4312 is taken and the methodreturns to block 4308 where one or more of the active floor tile and theserver rack measures the weight of the server rack. Returning todecision block 4310, if the measured weight has changed, the “YES”branch is taken, one or more of a TMC and a RMC provides an alert thatthe weight of the server rack has been changed in block 4314, and themethod returns to block 4308 where one or more of the active floor tileand the server rack measures the weight of the server rack. For exampleone or more pieces of equipment can have been removed from or installedinto server rack 2100, and one or more of TMC 2010 and RMC 2110 canprovide an alert to a DCMC, indicating that the one or more pieces ofequipment have been removed or installed into the server rack. Returningto decision block 4312, if the measured weight is greater than theweight limit information, the “YES” branch is taken, one or more of aTMC and a RMC provides an alert that the weight of the server rack isgreater than the weight limit in block 4316, and the method returns toblock 4308 where one or more of the active floor tile and the serverrack measures the weight of the server rack. For example one or more ofTMC 2010 and RMC 2110 can provide an alert to a DCMC, indicating thatthe weight of the server rack is greater than the weight limit.

FIG. 44 illustrates a method for providing a position indication forleveling feet of a server rack beginning at block 4402 where theposition of a leveling foot of a server rack is detected. For example,server rack 2200 can include a foot assembly 2210 and a weight assembly2220, and the weight assembly can be configured to determine if the footassembly is raised or lowered. A RMC provides an indication as to theposition of the leveling foot in block 4404, and the method ends inblock 4406. For example, a RMC of server rack 2200 can receive anindication from weight assembly 2220 as to the position of foot assembly2210, and can provide the indication as a visual indication on theserver rack, as an indication on a display, or another indication asneeded or desired.

FIG. 45 illustrates a method for leveling a server rack beginning atblock 4502. A RMC detects the level of a server rack in. block 4504. Forexample, server rack 2300 can include a leveling module for detectingthe level of the server rack. A decision is made as to whether or notthe server rack is level in decision block 4506. If so, the “YES” branchof decision block 4506 is taken and the method ends at block 4508. Ifthe server rack is not level, the “NO” branch of decision block 4506 istaken, the RMC actuates the leveling feet of the server rack to levelthe server rack in block 4510, and the method returns to block 4504where the RMC detects the level of the server rack. For example,leveling module 2350 can actuate adjusting servo 2316 to raise or lowerfoot 2312, as needed to bring server rack 2300 into level.

FIG. 46 illustrates a method for locking equipment into an unbalancedserver rack beginning at block 4602 where a RMC determines the weight ofthe equipment installed in the server rack. The RMC determines a centeror gravity for the equipment in a server rack in block 4604. Forexample, RMC 2410 can determine that the center of gravity 2475 forservers 2440, 2445, 2450, 2455, and 2460, or center of gravity 2477 forservers 2455 and 2460. A determination is made as to whether or not thecenter of gravity is above a centerline of the server rack in decisionblock 4606. If not, the “NO” branch of decision block 4606 is taken, theequipment in the server rack is un-locked in block 4612, and the methodends in block 4614. For example, center of gravity 2475 can be belowcenterline 2470, and interlocks 2422-2432 can be operated in the openposition to permit the installation and removal of servers 2440, 2445,2450, 2455, and 2460. If the center of gravity is above a centerline ofthe server rack, the “YES” branch of decision block 4606 is taken, andthe equipment in the server rack is locked in block 4608. For examplecenter of gravity 2477 can be above centerline 2470, and interlocks2422-2432 can be operated in the closed position to prevent the removalof servers 2455 and 2460. A decision is made as to whether or not theinterlock is overridden in decision block 4610. If so, the “YES” branchof decision block 4610 is taken, the equipment in the server rack isun-locked block 4612, and the method ends in block 4614. If theinterlock is not overridden, the “NO” branch of decision block 4610 istaken and the method ends at block 4614.

FIG. 47 illustrates a method for detecting a panel in a server rackbeginning at block 4702 where a RMC detects whether or not a panel isinstalled on a server rack, and whether or not an installed panel isgrounded. For example, RMC 2610 can operate to detect the presence orabsence of panel 2640, and whether or not the panel is grounded. Adecision is made as to whether or not the panel is present in the serverrack in decision block 4704. If so, the “YES” branch of decision block4704 is taken and a decision is made as to whether or not the detectedpane is grounded in decision block 4706. If so, the “YES” branch ofdecision block 4706 is taken and the method ends at block 4712.Returning to decision block 4704, if the panel is not present in theserver rack, the “NO” branch is taken, the RMC provides an alert thatindicates that the panel is missing from the server rack in block 4708,and the method ends in block 4712. Returning to decision block 4706, ifthe panel is not grounded, the “NO” branch is taken, the RMC provides analert that indicates that the panel is not grounded in block 4710, andthe method ends in block 4712.

FIG. 48 illustrates a method for managing a data center beginning atblock 4802 where a RMC determines the location of equipment in a serverrack. For example, a RMC can determine the location of the equipment byone or more of the methods described herein in FIGS. 33 and 36. The RMCcommunicates the location information to a DCMC in block 4804. The DCMCprovides an indication of the location information in block 4806, andthe method ends in block 4808. For example, DCMC 150 can provide theindication via one or more of a management system of data center 100 anda data center management appliance 2710.

FIG. 49 illustrates a method for setting up a data center beginning atblock 4902 where a DCMC is provided with a pre-determined list ofactivities to perform when a server rack is installed in a data center.The pre-determined list can include preset server names, prefixes, IPaddresses, BMC names, and the like for the servers or server racks,other server configuration information, such as OS installationinstructions, application software installation instructions, vLANmappings, and the like, as needed or desired. A server rack is installedin the data center in block 4904, the servers and server rack areconfigure by the DCMC based upon the pre-determined list in block 4906,and the method ends in block 4908.

FIG. 50 illustrates a method for repairing a data center beginning atblock 5002 where a DCMC identifies a problem in a data center. The DCMCprovides a map to the problem in block 5004. For example, DCMC 1500 canprovide the map to a problem via a data center management appliance2710, providing a visual representation of the location of theequipment. The DCMC provides repair instructions to fix the problem inblock 5006, and the method ends in block 5008. For example, the repairguide can include instructions for replacing a field replaceable unit(FRU) such as a disk drive, a power module, or the like.

FIG. 51 illustrates a generalized embodiment of information handlingsystem 5100. For purpose of this disclosure information handling system5100 can include any instrumentality or aggregate of instrumentalitiesoperable to compute, classify, process, transmit, receive, retrieve,originate, switch, store, display, manifest, detect, record, reproduce,handle, or utilize any form of information, intelligence, or data forbusiness, scientific, control, entertainment, or other purposes. Forexample, information handling system 100 can be a personal computer, alaptop computer, a smart phone, a tablet device or other consumerelectronic device, a network server, a network storage device, a switchrouter or other network communication device, or any other suitabledevice and may vary in size, shape, performance, functionality, andprice. Further, information handling system 100 can include processingresources for executing machine-executable code, such as a centralprocessing unit (CPU), a programmable logic array (PLA), an embedded.device such as a System-on-a-Chip (SoC), or other control logichardware. Information handling system 5100 can also include one or morecomputer-readable medium for storing machine-executable code, such assoftware or data. Additional components of information handling system5100 can include one or more storage devices that can storemachine-executable code, one or more communications ports forcommunicating with external devices, and various input and output (I/O)devices, such as a keyboard, a mouse, and a video display. Informationhandling system 5100 can also include one or more buses operable totransmit information between the various hardware components.

Information handling system 5100 can include devices or modules thatembody one or more of the devices or modules described above, andoperates to perform one or more of the methods described above.Information handling system 5100 includes a processors 5102 and 5104, achipset 5110, a memory 5120, a graphics interface 5130, include a basicinput and output system/extensible firmware interface (BIOS/EFI) module5140, a disk controller 5150, a disk emulator 5160, an input/output(I/O) interface 5170, and a network interface 5180. Processor 5102 isconnected to chipset 5110 via processor interface 5106, and processor5104 is connected to the chipset via processor interface 5108. Memory5120 is connected to chipset 5110 via a memory bus 5122. Graphicsinterface 5130 is connected to chipset 5110 via a graphics interface5132, and provides a video display output 5136 to a video display 5134.In a particular embodiment, information handling system 5100 includesseparate memories that are dedicated to each of processors 5102 and 5104via separate memory interfaces. An example of memory 5120 includesrandom access memory (RAM) such as static RAM (SRAM), dynamic RAM(DRAM), non-volatile RAM (NV-RAM), or the like, read only memory (ROM),another type of memory, or a combination thereof.

BIOS/EFI module 5140, disk controller 5150, and I/O interface 5170 areconnected to chipset 5110 via an I/O channel 5112. An example of I/Ochannel 5112 includes a Peripheral Component Interconnect (PCI)interface, a PCI-Extended (PCI-X) interface, a high-speed PCI-Express(PCIe) interface, another industry standard or proprietary communicationinterface, or a combination thereof. Chipset 5110 can also include oneor more other I/O interfaces, including an Industry StandardArchitecture (ISA) interface, a Small Computer Serial Interface (SCSI)interface, an Inter-Integrated Circuit (I²C) interface, a System PacketInterface (SPI), a Universal Serial Bus (USB), another interface, or acombination thereof. BIOS/EFI module 5140 includes BIOS/EFI codeoperable to detect resources within information handling system 5100, toprovide drivers for the resources, initialize the resources, and accessthe resources. BIOS/EFI module 5140 includes code that operates todetect resources within information handling system 5100, to providedrivers for the resources, to initialize the resources, and to accessthe resources.

Disk controller 5150 includes a disk interface 5152 that connects thedisc controller to a hard disk drive (HDD) 5154, to an optical diskdrive (ODD) 5156, and to disk emulator 5160. An example of diskinterface 5152 includes an Integrated Drive Electronics (IDE) interface,an Advanced Technology Attachment (ATA) such as a parallel ATA (PATA)interface or a serial ATA (SATA) interface, a SCSI interface, a USBinterface, a proprietary interface, or a combination thereof. Diskemulator 5160 permits a solid-state drive 5164 to be connected toinformation handling system 5100 via an external interface 5162. Anexample of external interface 5162 includes a USB interface, an IEEE1394 (Firewire) interface, a proprietary interface, or a combinationthereof. Alternatively, solid-state drive 5164 can be disposed withininformation handling system 5100.

I/O interface 5170 includes a peripheral interface 5172 that connectsthe I/O interface to an add-on resource 5174 and to network interface5180. Peripheral interface 5172 can be the same type of interface as I/Ochannel 5112, or can be a different type of interface. As such, I/Ointerface 5170 extends the capacity of I/O channel 5112 when peripheralinterface 5172 and the I/O channel are of the same type, and the I/Ointerface translates information from a format suitable to the I/Ochannel to a format suitable to the peripheral channel 5172 when theyare of a different type. Add-on resource 5174 can include a data storagesystem, an additional graphics interface, a network interface card(NIC), a sound/video processing card, another add-on resource, or acombination thereof. Add-on resource 5174 can be on a main circuitboard, on separate circuit board or add-in card disposed withininformation handling system 5100, a device that is external to theinformation handling system, or a combination thereof.

Network interface 5180 represents a NIC disposed within informationhandling system 5100, on a main circuit board of the informationhandling system, integrated onto another component such as chipset 5110,in another suitable location, or a combination thereof. Networkinterface device 5180 includes network channels 5182 and 5184 thatprovide interfaces to devices that are external to information handlingsystem 5100. In a particular embodiment, network channels 5182 and 5184are of a different type than peripheral channel 5172 and networkinterface 5180 translates information from a format suitable to theperipheral channel to a format suitable to external devices. An exampleof network channels 5182 and 5184 includes InfiniBand channels, FibreChannel channels, Gigabit Ethernet channels, proprietary channelarchitectures, or a combination thereof. Network channels 5182 and 5184can be connected to external network resources (not illustrated). Thenetwork resource can include another information handling system, a datastorage system, another network, a grid management system, anothersuitable resource, or a combination thereof.

The skilled artisan will recognize that, where a particular device type,standard, or operation is specified, that suitable alternatives asneeded or desired can be incorporated along with the teachings herein.For example, where the present disclosure describes networkcommunications such as Ethernet communications, other communicationstandards, hardware, or software can be utilized to providecommunications of sufficient bandwidth to perform the operations,teachings, and methods as disclosed herein.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. A server rack comprising: a power mapping module;a power receptacle coupled to the power mapping module and including afirst power line communication module, wherein the power receptacle is:uniquely associated with a rack unit of the server rack; and collocatedwith the associated rack unit; and a server installed into the rack unitand including a second power line communication module, the server beingcoupled to the power mapping module via a management network, whereinthe server asserts an interrupt request to the power mapping module viathe management network; wherein: the power mapping module sends a uniqueidentifier via the first power line communication module in response toreceiving the interrupt request; the server receives the uniqueidentifier via the second power line communication module and sends theunique identifier to the power mapping module via the managementnetwork; and the power mapping module determines that the server isinstalled into the rack based upon the receipt of the unique identifier.2. The server rack of claim 1, wherein the power mapping moduledetermines a physical location of the server based upon the powerreceptacle being collocated with the rack unit.
 3. The server rack ofclaim 2, wherein: the management network includes a data centermanagement controller; and the power mapping module further provides thephysical location of the server to the data center managementcontroller.
 4. The server rack of claim 1, further comprising: a powerdistribution unit, wherein the power mapping module and the powerreceptacle are integrated with the power distribution unit.
 5. Theserver rack of claim 1, wherein the server includes a managementcontroller coupled to the second power line communication module.
 6. Theserver rack of claim 5, wherein the management controller is operable tomanage the server via the second power line communication module.
 7. Theserver rack of claim 1, wherein the server acknowledges the receipt ofthe unique identifier via the second power line communication module. 8.A server rack comprising: a power mapping module; a power receptaclecoupled to the power mapping module and including a first power linecommunication module, wherein the power receptacle is: uniquelyassociated with a rack unit of the server rack; and collocated with theassociated rack unit; and a server installed into the rack unit andincluding a second power line communication module, the server beingcoupled to the power mapping module via a management network, whereinthe server asserts an interrupt request to the power mapping module viathe management network; wherein: the power mapping module sends a uniqueidentifier to the server via the management network in response toreceiving the interrupt request; the server receives the uniqueidentifier and sends the unique identifier to the power mapping modulevia the second power line communication module; and the power mappingmodule determines that the server is installed into the rack based uponthe receipt of the unique identifier.
 9. The server rack of claim 8,wherein the power mapping module determines a physical location of theserver based upon the power receptacle being collocated with the rackunit.
 10. The server rack of claim 9, wherein: the management networkincludes a data center management controller; and the power mappingmodule further provides the physical location of the server to the datacenter management controller.
 11. The server rack of claim 8, furthercomprising: a power distribution unit, wherein the power mapping moduleand the power receptacle are integrated with the power distributionunit.
 12. The server rack of claim 8, wherein the server acknowledgesthe receipt of the unique identifier via, the second power linecommunication module.
 13. The server rack of claim 8, wherein the serverincludes a management controller coupled to the second power linecommunication module.
 14. The server rack of claim 13, wherein themanagement controller is operable to manage the server via the secondpower line communication module.
 15. A server rack comprising: a powermapping module; a power receptacle coupled to the power mapping moduleand including a first power line communication module, wherein the powerreceptacle is: uniquely associated with a rack unit of the server rack;and collocated with the associated rack unit; and a server installedinto the rack unit and including a second power line communicationmodule, the server being coupled to the power mapping module via amanagement network, wherein the server: sends a unique identifier to thepower mapping module via the management network; and sends the uniqueidentifier to the power mapping module via the second power linecommunication module; wherein the power mapping module determines thatthe server is installed into the rack based upon the receipt of theunique identifier via the management network and the second power linecommunication module.
 16. The server rack of claim 15, wherein the powermapping module determines a physical location of the server based uponthe power receptacle being collocate with the rack unit.
 17. The serverrack of claim 16, wherein: the management network includes a data centermanagement controller; and the power mapping module further provides thephysical location of the server to the data center managementcontroller.
 18. The server rack of claim 15, further comprising: a powerdistribution unit, wherein the power mapping module and the powerreceptacle are integrated with the power distribution unit.
 19. Theserver rack of claim 15, wherein the server acknowledges the receipt ofthe unique identifier via the second power line communication module.20. The server rack of claim 15, wherein the server includes amanagement controller coupled to the second power line communicationmodule.